Severity by source
AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L
Dual prerequisite of dynamic link mode plus disabled encryption justifies AC:H; unauthenticated spoofing needs no privileges; injection yields only integrity and availability impact.
Primary rating from Vendor (redhat).
CVSS VectorVendor: redhat
Lifecycle Timeline
2DescriptionCVE.org
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.
AnalysisAI
ACL bypass in kronosnet (versions ≤ 1.34) allows remote unauthenticated attackers to inject arbitrary data packets into cluster communication channels under a specific dual-condition deployment configuration. By spoofing a valid link ID in crafted network frames, an attacker circumvents the ACL subsystem entirely, potentially causing data corruption or service instabilities in clustering stacks shipped with Red Hat Enterprise Linux 8, 9, 10 and OpenShift Container Platform 4. No public exploit code and no active exploitation have been identified at time of analysis.
Technical ContextAI
kronosnet (libknet) is a network abstraction layer designed for high-availability clustering, providing multi-link failover, heartbeat management, and optional payload encryption via NSS or libgcrypt backends. Its ACL subsystem controls which hosts may participate in cluster communication. CWE-290 (Authentication Bypass by Spoofing) describes the root cause: when dynamic link mode is active - meaning the framework accepts traffic from any source IP rather than a static allowlist - and encryption is disabled, the ACL validation logic implicitly trusts the link ID field embedded in incoming packet headers without cryptographic verification. Because no encryption is present to authenticate packet origin or integrity, that field is trivially spoofable. The CPE strings (cpe:2.3:a:red_hat:red_hat_enterprise_linux_8, _9, _10, and openshift_container_platform_4) identify the Red Hat delivery platforms; the vulnerable binary is the kronosnet library itself at version 1.34 and below.
RemediationAI
No specific patched kronosnet version is identified in the available references; consult the Red Hat advisory at https://access.redhat.com/security/cve/CVE-2026-15812 and track fix progress at https://bugzilla.redhat.com/show_bug.cgi?id=2500851 for updated package versions as they are released. The most effective immediate compensating control is enabling kronosnet's built-in payload encryption using the nss or gcrypt crypto model in the cluster configuration; once encryption is active, all packets carry cryptographic authentication that renders link ID spoofing ineffective regardless of link mode. Alternatively, replace dynamic link mode with static ACL peer definitions that enumerate allowed source IP addresses, eliminating the condition under which the untrusted link ID is accepted. Both workarounds eliminate the attack surface entirely but require cluster configuration changes and coordinated restarts of affected clustering services (corosync and pacemaker), which may cause brief service interruption. Enabling encryption also carries a modest CPU overhead on high-throughput cluster heartbeat traffic, which should be evaluated for latency-sensitive environments.
More in Red Hat Enterprise Linux 10
View allHeap corruption via double-free in 389-ds-base's LDAP control parsing allows an unauthenticated remote attacker to crash
Remote code execution in Cockpit's web interface allows unauthenticated attackers to execute arbitrary commands on the h
Remote code execution in Samba's printing subsystem allows remote attackers to inject arbitrary shell commands via craft
Authentication bypass in 389 Directory Server (shipped as Red Hat Directory Server 11-13 and within RHEL 6-10) lets remo
Remote code execution and privilege escalation in HPLIP (HP Linux Imaging and Printing) affects the hpcups print filter
Unauthenticated privilege escalation in FreeIPA (Red Hat Identity Management) allows a remote attacker to gain genuine a
Remote code execution in libarchive on 32-bit systems allows unauthenticated attackers to execute arbitrary code via spe
HTTP request smuggling in Undertow (the embedded web server underpinning JBoss EAP, Red Hat Data Grid, and Apache Camel
HTTP request smuggling in Red Hat Undertow allows remote unauthenticated attackers to bypass front-end security controls
Out-of-bounds read in the GnuTLS DTLS handshake reassembly logic lets remote unauthenticated attackers trigger an intege
HTTP request smuggling in Undertow allows remote unauthenticated attackers to send `\r\r\r` as a header block terminator
Local privilege escalation in Performance Co-Pilot (PCP) on Red Hat Enterprise Linux 6 through 10 and OpenShift Containe
Same weakness CWE-290 – Authentication Bypass by Spoofing
View allSame technique Authentication Bypass
View allVendor StatusVendor
SUSE
Severity: Moderate| Product | Status |
|---|---|
| SUSE Linux Enterprise High Availability Extension 16.0 | Affected |
| SUSE Linux Enterprise High Availability Extension 16.1 | Affected |
| SUSE Linux Enterprise Server for SAP applications 16.0 | Affected |
| SUSE Linux Enterprise Server for SAP applications 16.1 | Affected |
| openSUSE Leap 16.0 | Affected |
Share
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-46152
GHSA-36hw-mpc9-fw23