KeePass vulnerabilities: known CVEs & security history
KeePass · Password manager · 7 tracked CVEs · 0 actively exploited · updated June 2026 · what is a CVE? →
This is the full list of known vulnerabilities (CVEs) across all KeePass release lines — 7 in total. A CVE here doesn't mean your version is affected — check KeePass's current status and the safe version to run.
Known KeePass CVEs
Actively-exploited and most-severe first. Open any CVE for full details.
| CVE | Severity | CVSS | EPSS | Year |
|---|---|---|---|---|
| CVE-2019-20184 | high | 7.8 | 2% | 2020 |
| CVE-2023-32784 | high | 7.5 | 5% | 2023 |
| CVE-2022-0725 | high | 7.5 | 2% | 2022 |
| CVE-2017-1000066 | high | 7.5 | 1% | 2017 |
| CVE-2016-5119 | high | 7.5 | 2% | 2017 |
| CVE-2010-5200 | medium | 6.9 | 0% | 2012 |
| CVE-2023-24055 | medium | 5.5 | 4% | 2023 |
Is my KeePass version affected?
The list above spans every release. To know whether your version is affected — and the minimum safe version to upgrade to — check it directly.
Check your KeePass version → · Monitor KeePass for new CVEs →
KeePass vulnerabilities — frequently asked
How many known vulnerabilities does KeePass have?
IsItPatched tracks 7 CVEs for KeePass. 0 are critical-severity and 5 high-severity. These span every release line — what matters is whether the version you run is affected.
Does KeePass have any actively-exploited vulnerabilities?
None of KeePass's tracked CVEs are currently in CISA's KEV catalog — but new ones can be added at any time, so keep your version current.
What is the most severe KeePass vulnerability?
Among tracked issues, CVE-2019-20184 (HIGH, CVSS 7.8) ranks highest — a CWE-1236 weakness.
Is KeePass safe to use?
It depends on the version. The latest supported KeePass release clears the known issues; older versions may still be affected. Check the exact version you run for a verdict.
CVE data aggregated from NVD, CISA KEV and EPSS (FIRST.org). Related: KeePass security status · KeePass end-of-life · actively-exploited CVEs. Always verify against KeePass's advisories — see our disclaimer.