A vulnerability was found in kronosnet's (version <=1.34) cryptographic configuration management. The framework does not correctly zero-out or wipe sensitive memory segments after executing changes to its cryptographic configuration. This omission leaves raw encryption keys resident in memory after the associated structures are freed. A local attacker capable of leveraging memory disclosure techniques could exploit this flaw to retrieve the active encryption key, allowing them to decrypt cluster network communications or inject malicious packets to cause severe high-availability cluster instability.
CVE-2026-15811
MEDIUMPre-NVD 5.85.8—Trending — 4 sources updated this week
EchelonGraph scoreHIGH confidence
Score 5.8 from GitHub Security Advisory published 2026-07-21. a secondary CVSS source baseline 5.8; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: ghsa, secondary
5.8
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.8Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.8
- EG Score
- 5.8(high)
- EPSS
- 0.0%
- KEV
- Not listed
Published
July 21, 2026
Last Modified
July 21, 2026
Advisory Details (2)
Auto-updated Jul 21, 2026Patch available. Sources: redhat.
redhat Patch Available
2500849 – (CVE-2026-15811) CVE-2026-15811 kronosnet: kronosnet: encryption key exposure in memory after cryptographic configuration changes
https://bugzilla.redhat.com/show_bug.cgi?id=2500849Vendor Advisories for CVE-2026-15811(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 5× in last 7d / 5× 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.
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-21 06:49 UTCEG score recompute
- 2026-07-21 06:49 UTCGHSA enrichment
- 2026-07-21 05:44 UTCEG score recompute
- 2026-07-21 05:43 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-15811?
CVE-2026-15811 is a medium vulnerability published on July 21, 2026. A vulnerability was found in kronosnet's (version <=1.34) cryptographic configuration management. The framework does not correctly zero-out or wipe sensitive memory segments after executing changes to its cryptographic configuration. This omission leaves raw encryption keys resident in memory after…
When was CVE-2026-15811 disclosed?
CVE-2026-15811 was first published in the National Vulnerability Database on July 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-15811 actively exploited?
CVE-2026-15811 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-15811?
CVE-2026-15811 has a CVSS v3 base score of 5.8 (NVD).
How do I remediate CVE-2026-15811?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-15811, 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-15811
Is Your Infrastructure Affected by CVE-2026-15811?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.