Is CVE-2026-15812 exploited in the wild?

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

How severe is CVE-2026-15812?

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

Is there a fix for CVE-2026-15812?

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-15812 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-15812?

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-15812: kronosnet ACL bypass via link ID spoofing on unencrypted dynamic links

CVE-2026-15812 · Severity: medium · CVSS 4.8 · Published 2026-07-21

Kronosnet, a networking tool used to connect multiple computers in a cluster, contains a security flaw in how it verifies incoming data. When configured to accept connections from any address without encryption, the system fails to properly check if the sender is who they claim to be. An attacker could exploit this to bypass security controls and send unauthorized data into the network, potentially causing data corruption or system crashes.

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-15812 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-15812 being exploited in the wild.
How severe is CVE-2026-15812?: Medium severity, with a CVSS score of 4.8, published 21 July 2026.
Which products and versions are affected?: Kronosnet <= 1.34.
Is there a fix for CVE-2026-15812?: 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-15812 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-15812?: 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 logical flaw exists in the internal Access Control List (ACL) subsystem of kronosnet when configured to manage dynamic links without network payload encryption. The validation architecture implicitly trusts the link ID provided within incoming data packets without cryptographic verification. A remote, unauthenticated attacker can exploit this by spoofing a legitimate link ID inside crafted network frames. This allows the attacker to bypass the ACL framework and inject arbitrary data packets into the application layer, potentially leading to data corruption or service instability. The vulnerability affects kronosnet versions 1.34 and earlier.

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: Reported to 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.