CVE-2026-86776

LOWPre-NVD 3.33.3—
EchelonGraph scoreHIGH confidence

Score 3.3 from GitHub Security Advisory published 2026-09-09. a secondary CVSS source baseline 3.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
3.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 3.3Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
3.3
EG Score
3.3(high)
EG Risk
31(Track)
EG Risk 31/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity33% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

September 9, 2026

Last Modified

September 10, 2026

References (4)

Vendor Advisories for CVE-2026-86776(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 21× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-17 19:32 UTCEPSS rescore
  3. 2026-09-17 01:13 UTCEG score recompute
  4. 2026-09-17 01:13 UTCGHSA enrichment
  5. 2026-09-16 14:09 UTCEPSS rescore
  6. 2026-09-16 05:15 UTCEPSS rescore
  7. 2026-09-15 03:12 UTCEPSS rescore
  8. 2026-09-15 03:12 UTCEPSS rescore
  9. 2026-09-13 22:38 UTCEG score recompute
  10. 2026-09-13 22:38 UTCGHSA enrichment
  11. 2026-09-11 14:53 UTCEPSS rescore
  12. 2026-09-11 14:53 UTCEPSS rescore
  13. 2026-09-10 20:04 UTCEG score recompute
  14. 2026-09-10 20:04 UTCGHSA enrichment
  15. 2026-09-10 15:22 UTCEG score recompute
  16. 2026-09-10 15:22 UTCGHSA enrichment
  17. 2026-09-10 15:00 UTCEG score recompute
  18. 2026-09-10 15:00 UTCGHSA enrichment
  19. 2026-09-09 10:24 UTCEG score recompute
  20. 2026-09-09 10:15 UTCEG score recompute
  21. 2026-09-09 10:15 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-86776?
CVE-2026-86776 is a low vulnerability published on September 9, 2026. 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…
When was CVE-2026-86776 disclosed?
CVE-2026-86776 was first published in the National Vulnerability Database on September 9, 2026, with the most recent update on September 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-86776 actively exploited?
CVE-2026-86776 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 98.1% of all scored CVEs.
What is the CVSS score of CVE-2026-86776?
CVE-2026-86776 has a CVSS v3 base score of 3.3 (NVD).
How do I remediate CVE-2026-86776?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-86776, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-86776

Explore →

Is Your Infrastructure Affected by CVE-2026-86776?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs