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
Score 5.8 from GitHub Security Advisory published 2026-07-21. a secondary CVSS source baseline 5.8; sources differ by 0.0.
- Lower severity and no public exploit yet
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)
- EG Risk
- 26(Track)EG Risk 26/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 computedSeverity58% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 0%
- KEV
- Not listed
Published
July 21, 2026
Last Modified
July 23, 2026
Advisory Details (2)
Auto-updated Jul 21, 20262500849 – (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 13× in last 7d / 13× 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-27 04:41 UTCEG score recompute
- 2026-07-27 04:41 UTCGHSA enrichment
- 2026-07-26 04:24 UTCEG score recompute
- 2026-07-26 04:24 UTCGHSA enrichment
- 2026-07-24 14:17 UTCEPSS rescore
- 2026-07-23 03:05 UTCEG score recompute
- 2026-07-22 23:20 UTCEG score recompute
- 2026-07-22 23:20 UTCGHSA enrichment
- 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?
When was CVE-2026-15811 disclosed?
Is CVE-2026-15811 actively exploited?
What is the CVSS score of CVE-2026-15811?
How do I remediate CVE-2026-15811?
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.