CVE-2026-15811
MediumCVSS 5.8Exploitation Probability (EPSS)
Low risk0th percentile - higher than 0% of all known CVEs
Summary
In kronosnet (version <=1.34), the framework does not wipe sensitive memory after cryptographic configuration changes, leaving encryption keys in memory. A local attacker can retrieve them to decrypt cluster communications or inject malicious packets.
Risk Assessment
Risk of complete compromise of high-availability cluster communication, including traffic decryption and cluster destabilization.
Recommendation
Update kronosnet to version 1.35 or later, which includes a memory cleanup fix.
Other vulnerabilities in kronosnet
See all- CVE-2026-15812Medium
In the ACL subsystem of kronosnet (versions <= 1.34), when configured for dynamic links without encryption, the validation trusts the link ID from packets. A remote unauthenticated attacker can spoof the link ID and bypass ACL, injecting arbitrary packets into the application layer.
- CVE-2026-15813Medium
Vulnerability in the network packet de-fragmentation engine of kronosnet (versions <= 1.34). The reassembly code does not properly validate sequence numbers of fragments, allowing an attacker to send malformed packets. This can lead to out-of-bounds memory access or heap corruption, causing application crashes or system instability.
Original NVD description (English source)
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.