Security readout for executives and security teams
Plain-English summary
Keygraph Shannon includes a hard-coded router API key. If the router is enabled and reachable, an unauthenticated network attacker could authenticate with the static key, route requests through the victim instance, consume upstream API credits, and potentially expose proxied request or response data.
Executive priority
Treat this as high priority for any internet-exposed or partner-accessible Shannon deployment. The business risk is unauthorized API consumption, unexpected provider costs, and potential disclosure of proxied data. Prioritize exposure discovery before broad emergency action.
Technical view
This is CWE-798: use of hard-coded credentials in Shannon router configuration. CVSS is 7.3 high: network exploitable, low complexity, no privileges or user interaction. Sources say general exploitability was mitigated by commit 023cc95, but affected release and upgrade guidance are not fully specified.
Likely exposure
Exposure is most likely where Shannon’s router component is enabled and its router port is reachable from the internet or untrusted networks. Systems without the router enabled, or with strict network access controls, appear less exposed based on the source description.
Exploitation context
The provided sources do not show CISA KEV listing or confirmed active exploitation. The issue is still serious because a reachable router could allow unauthorized authenticated proxying using a static credential and the victim’s configured upstream provider credentials.
Researcher notes
The source bundle names KeygraphHQ Shannon with version data listed only as “0” and default status unknown, so affected-version precision is limited. The strongest technical anchors are the hard-coded credential description, CVSS vector, GitHub issue/PR, and mitigation commit reference.
Mitigation direction
- Apply vendor guidance or a Shannon build containing commit 023cc95.
- Disable the router component if it is not required.
- Restrict router access to trusted networks only.
- Rotate upstream provider API credentials if exposure is suspected.
- Review API provider usage for unexpected traffic or charges.
Validation and detection
- Inventory Shannon deployments and identify enabled router components.
- Confirm whether any router port is reachable from untrusted networks.
- Check whether the deployed build includes commit 023cc95 or later remediation.
- Review logs for unexpected router authentication or proxied requests.
- Compare upstream API usage against expected Shannon workloads.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-798: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-29023 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L3.93.4VulnCheckCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N——VulnCheckVulnerability scoring details
Base CVSS 4.0 score
6.9MediumVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N
Base CVSS 3.1 score
7.3HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/KeygraphHQ/shannon/issues/186CVE reference, VulnCheck · issue-tracking
- https://github.com/KeygraphHQ/shannon/pull/224CVE reference, VulnCheck · issue-tracking
- https://github.com/KeygraphHQ/shannon/pull/224/changes/023cc953db742602964b7826105278d15c28a420CVE reference, VulnCheck · issue-tracking
- https://www.vulncheck.com/advisories/keygraph-shannon-hard-coded-router-api-keyCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Use of Hard-coded Credentials
Use of Hard-coded Credentials represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.