Is CVE-2026-15811 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-15811 being exploited in the wild.

How severe is CVE-2026-15811?

Medium severity, with a CVSS score of 5.8, published 21 July 2026.

Is there a fix for CVE-2026-15811?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-15811 attacked?

It is attacked with local access, in a software library.

Am I affected by CVE-2026-15811?

Check whether you run Kronosnet, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 8 or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-15811: Kronosnet improper memory clearing in cryptographic configuration

CVE-2026-15811 · Severity: medium · CVSS 5.8 · Published 2026-07-21

Kronosnet, a networking library used to manage high-availability clusters, fails to properly clear sensitive data from system memory after changing its security settings. This flaw could allow a local attacker to recover secret encryption keys that remain in memory. With these keys, an attacker could eavesdrop on private cluster communications or disrupt the stability of the entire server cluster.

Technologies: Kronosnet, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 8, Red Hat Enterprise Linux 9, Red Hat OpenShift Container Platform 4. Vendors: Kronosnet, Red Hat.

Quick answers

Is CVE-2026-15811 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-15811 being exploited in the wild.
How severe is CVE-2026-15811?: Medium severity, with a CVSS score of 5.8, published 21 July 2026.
Which products and versions are affected?: Kronosnet <=1.34.
Is there a fix for CVE-2026-15811?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-15811 attacked?: It is attacked with local access, in a software library.
Am I affected by CVE-2026-15811?: Check whether you run Kronosnet, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 8 or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A vulnerability exists in kronosnet (version 1.34 and earlier) within its cryptographic configuration management. The framework fails to explicitly wipe or zero-out sensitive memory structures (using routines like memset_s) before they are freed or reallocated during configuration changes. This results in raw cryptographic key material remaining resident in unallocated heap memory. A local attacker capable of leveraging memory disclosure techniques or inspecting uninitialized heap segments can recover these keys. Successful exploitation allows for the decryption of cluster network communications or the injection of unauthorized packets, potentially leading to cluster instability.

Affected products

kronosnet kronosnet <=1.34
Red Hat Red Hat Enterprise Linux 8
Red Hat Red Hat Enterprise Linux 9
Red Hat Red Hat Enterprise Linux 10
Red Hat Red Hat OpenShift Container Platform 4

Timeline

2026-07-15: disclosed: Initial report in Red Hat Bugzilla
2026-07-21: advisory: NVD publication date

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.