KeePass 2.35 through 2.61.1 Memory Exhaustion via KDBX Header Field Size
Key facts
- Attack vector
- Local
- Privileges required
- None
- User interaction
- Active
- Attack complexity
- Low
- Attack requirements
- None
- Impact type
- Denial of service
- Confidentiality · integrity · availability
- None · None · Low
- Fix status
- No fix listed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-789.
Summary
KeePass versions 2.35 through 2.61.1 fail to validate KDBX header field sizes before memory allocation in the ReadHeaderField function. Attackers can craft a malicious KDBX file declaring excessive header field lengths to trigger allocation of gigabytes of memory, causing the application to consume resources and terminate.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- Poc
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
No fixed version listed by the sources yet.
Vendor assessments
Timeline
- 2026-10-02 Threatist record created from CVE-2026-86776
- 2026-10-03 Alias added: GHSA-5r36-v86r-vm5x
References
More KeePass vulnerabilities
- TI-2023-16037 In KeePass 2.x before 2.54, it is possible to recover the cleartext master password from… CVSS 3.1HIGH 7.5
- TI-2020-19313 KeePass 2.44 - Denial of Service (PoC) CVSS 4.0MEDIUM 4.6
- TI-2022-00638 Information disclosure in keepass CVSS 3.1HIGH 7.5
- TI-2019-14558 KeePass 2.4.1 allows CSV injection in the title field of a CSV export. CVSS 3.1HIGH 7.8
- TI-2016-04425 The automatic update feature in KeePass 2.33 and earlier allows man-in-the-middle… CVSS 3.0HIGH 7.5
- TI-2017-14405 The entry details view function in KeePass version 1.32 inadvertently decrypts certain… CVSS 3.0HIGH 7.5
Sources
- CVE-2026-86776 · CVE Program
- CVE-2026-86776 · NVD
- FIRST EPSS
- GHSA-5r36-v86r-vm5x · GitHub Advisory Database · CC BY 4.0
- CVE-2026-86776 · Red Hat security data · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences