Medium [CVE-2026-15812] access control list bypass via link ID spoofing on unencrypted dynamic links
This medium-severity Red Hat Linux advisory covers CVE-2026-15812 affecting Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 8, Red Hat Enterprise Linux 9.
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.
Summary
A vulnerability was found in the internal Access Control List (ACL) subsystem of kronosnet (Version affected: <= 1.34).
When the framework is explicitly configured to manage dynamic links (accepting network traffic from any IP address) without network payload encryption, the validation architecture implicitly trusts the link ID provided within incoming data packets.
A remote, unauthenticated attacker can exploit this lack of validation by spoofing a legitimate link ID inside crafted network frames. This allows the attacker to fully bypass the ACL framework and inject arbitrary data packets into the application layer, potentially leading to data corruption or service instabilities.
Red Hat Product Security rates this vulnerability's impact as Low. Although the vulnerability allows an unauthenticated remote attacker to completely bypass the internal ACL layer and introduce arbitrary traffic, it depends entirely on a non-production configuration.
The exploit requires that kronosnet actively accept connections from any arbitrary IP (dynamic links) while simultaneously running completely unencrypted traffic.
Furthermore, this issue does not affect Red Hat Enterprise Linux High Availability (RHEL HA) or any official layered products, as Red Hat configurations securely enable network encryption by default, entirely mitigating the vulnerability's attack prerequisites.
Fixed versions
No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.
Official advisory · high-confidence parse· fetched 6 days ago·verify at source
Mitigation
The source record does not include mitigation steps. That is not a statement that no fix exists — read the vendor advisory below for the authoritative guidance.
Official advisory · high-confidence parse· fetched 6 days ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.