Unauthorized API proxying via hard-coded router key
Published Mar 9, 2026 · Updated Mar 9, 2026
Authentication bypass in Keygraph Shannon allows remote attackers to proxy API requests through an exposed router using a public static key. The router configuration embeds shannon-router-key as APIKEY, while Docker Compose publishes TCP port 3456 on every host interface. Router mode must be enabled and the port network-reachable; successful access spends configured provider credentials and exposes proxied request and response data.
Summary
What happened
Authentication bypass in Keygraph Shannon allows remote attackers to proxy API requests through an exposed router using a public static key. The router configuration embeds shannon-router-key as APIKEY, while Docker Compose publishes TCP port 3456 on every host interface. Router mode must be enabled and the port network-reachable; successful access spends configured provider credentials and exposes proxied request and response data.
The record
- CVE
- CVE-2026-29023
- Published
- Mar 9, 2026
- Updated
- Mar 9, 2026
- Vendor
- Keygraph
- Product
- Shannon
- Classifications
- CWE-798, T1078
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 9, 2026CVE publishedPublication date reported by the CVE source.
- Mar 9, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <commit 023cc95
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo