Answer in brief
CVE-2026-15811 records a Medium severity (CVSS 5.8) vulnerability in Kronosnet: kronosnet: encryption key exposure in memory after cryptographic configuration changes. The current sources do not mark it as known exploited. The current feed maps Red Hat/kronosnet (generic), Red Hat/openshift/ose-rhel-coreos-9 (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Red Hat/kronosnet (generic), Red Hat/openshift/ose-rhel-coreos-9 (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Red Hat/kronosnetgeneric | * | Not reported |
| Red Hat/openshift/ose-rhel-coreos-9generic | * | Not reported |
Published upstream
Jul 21, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 21, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 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 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.
Quoted source text, attributed separately from HOL analysis.