In KeePass 2.x before 2.54, it is possible to recover the cleartext master password from a memory dump, even when a workspace is locked or n
In KeePass 2.x before 2.54, it is possible to recover the cleartext master password from a memory dump, even when a workspace is locked or no longer running. The memory dump can be a KeePass process dump, swap file (pagefile.sys), hibernation file (hiberfil.sys), or RAM dump of the entire system. The first character cannot be recovered. In 2.54, there is different API usage and/or random string insertion for mitigation.
- Published
- May 15, 2023
- Updated
- Jun 17, 2026
- EPSS
- 4.4% · 91th percentile
- CWE
- CWE-319
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 4.4%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| keepass | keepass | cpe:2.3:a:keepass:keepass |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- keepass keepass2.00 and later · before 2.54
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | keepass2 | all versions | — |
| openSUSE:Tumbleweed | keepass | before 2.54-1.1 | 2.54-1.1 |
| SUSE:Package Hub 15 SP4 | keepass | before 2.54-bp154.2.3.1 | 2.54-bp154.2.3.1 |
| SUSE:Package Hub 15 SP4 | keepass | before 2.54-bp154.2.3.1 | 2.54-bp154.2.3.1 |
| SUSE:Package Hub 15 SP5 | keepass | before 2.54-bp155.2.3.1 | 2.54-bp155.2.3.1 |
| SUSE:Package Hub 15 SP5 | keepass | before 2.54-bp155.2.3.1 | 2.54-bp155.2.3.1 |
Same product
keepass: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-0725A flaw was found in keepass.31Monitor
- CVE-2019-20184KeePass 2.4.1 allows CSV injection in the title field of a CSV export.31Monitor
- CVE-2016-5119The automatic update feature in KeePass 2.33 and earlier allows man-in-the-middle attackers to execute arbitrary code by spoofing the versio31Monitor
- CVE-2017-1000066The entry details view function in KeePass version 1.32 inadvertently decrypts certain database entries into memory, which may result in the30Monitor
- CVE-2010-5200Untrusted search path vulnerability in KeePass Password Safe before 1.18 allows local users to gain privileges via a Trojan horse DLL in the27Monitor
- CVE-2023-24055KeePass through 2.53 (in a default installation) allows an attacker, who has write access to the XML configuration file, to obtain the clear23Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| opensuse:keepass | 2.54-bp154.2.3.1 · openSUSE:Leap 15.4 | Package registry (OSV) |
| suse:keepass | 2.54-bp154.2.3.1 · SUSE:Package Hub 15 SP4 | Package registry (OSV) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×14
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:652 | 2023-05-01 |
| Proof-of-concept repository on GitHub | stars:2 | 2023-05-17 |
| Proof-of-concept repository on GitHub | stars:6 | 2023-05-20 |
| Proof-of-concept repository on GitHub | stars:29 | 2023-05-22 |
| Proof-of-concept repository on GitHub | stars:0 | 2023-06-04 |
| Proof-of-concept repository on GitHub | stars:0 | 2023-08-30 |
| Proof-of-concept repository on GitHub | stars:4 | 2024-02-01 |
| Proof-of-concept repository on GitHub | stars:0 | 2024-07-10 |
| Proof-of-concept repository on GitHub | stars:0 | 2024-12-04 |
| Proof-of-concept repository on GitHub | stars:0 | 2025-03-31 |
| Proof-of-concept repository on GitHub | stars:0 | 2026-03-24 |
| Proof-of-concept repository on GitHub | stars:0 | 2026-05-25 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- First PoC-14 d
- Published
- TodaySep 30, 2026+1235 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-319 · Cleartext Transmission of Sensitive InformationCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- github.com/keepassxreboot/keepassxc/discussions/9433
- sourceforge.net/p/keepass/discussion/329220/thread/f3438e6283/
Vendor advisories and official records. Exploit/PoC links are deliberately left out.