Bug 2500851 (CVE-2026-15812) - CVE-2026-15812 kronosnet: kronosnet: access control list bypass via link ID spoofing on unencrypted dynamic links
Summary: CVE-2026-15812 kronosnet: kronosnet: access control list bypass via link ID s...
Keywords:
Status: NEW
Alias: CVE-2026-15812
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 2500852
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-07-15 10:47 UTC by OSIDB Bzimport
Modified: 2026-07-20 07:32 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-07-15 10:47:32 UTC
Vulnerability Reference: A flaw was found in kronosnet's dynamic link validation process where it fails to safely verify packet origins, permitting an access control list (ACL) bypass via ID spoofing.

Component / Vulnerable Part: kronosnet -> Access Control List (ACL) engine for dynamic link handling (https://github.com/kronosnet/kronosnet/).

Technical Analysis & Root Cause: When kronosnet is configured to utilize dynamic links (allowing connections from any source IP address), it relies on an internal ACL structure mapped to internal link identifiers. A logical flaw exists within the dynamic packet processing pipeline where the authentication routine implicitly trusts the incoming frame's source payload metadata to determine the link ID. The validation logic does not cryptographically or cryptanalytically challenge the source identifier. Consequently, an adversary can craft network packets with a spoofed link ID matching an authorized node context, tricking the parser into circumventing ACL constraints.

Impact: A remote, unauthenticated attacker can exploit this flow to inject arbitrary data packets directly into the kronosnet interface. Depending on how the upper-layer application processes unexpected or untrusted data, this can trigger packet corruption or structural runtime instability.


Note You need to log in before you can comment on or make changes to this bug.