# CVE-2026-29023: Keygraph Shannon Hard-coded Router API Key

> Attackers can use a hard-coded API key to proxy requests through the Shannon router, leading to unauthorized API usage and data disclosure.

- **Severity:** Medium 6.9 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Mar 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-qrvr-jqxg-65rv

## What is CVE-2026-29023?

CVE-2026-29023 is a medium-severity vulnerability in KeygraphHQ Shannon, published on 9 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Keygraph Shannon contains a hard-coded API key in its router configuration that, when the router component is enabled and exposed, allows network attackers to authenticate using the publicly known static key. An attacker able to reach the router port can proxy requests through the Shannon instance using the victim’s configured upstream provider API credentials, resulting in unauthorized API usage and potential disclosure of proxied request and response data. This vulnerability's general exploitability has been mitigated with the introduction of commit 023cc95.

Weakness: CWE-798 (Use of Hard-coded Credentials)

## Which versions are affected by CVE-2026-29023?


## How do I fix CVE-2026-29023?

No fix has been published for CVE-2026-29023 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-29023 being exploited?

There is no known exploitation of CVE-2026-29023 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-29023 and fix it if it is affected.

What it is: CVE-2026-29023 is a medium-severity vulnerability in KeygraphHQ Shannon, published on 9 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-29023 in the wild and no public exploit code.

Affected product: KeygraphHQ Shannon. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-29023/ (Markdown: https://insights.sbomify.com/CVE-2026-29023/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-29023
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-29023
- OSV: https://osv.dev/vulnerability/CVE-2026-29023

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-29023/
Summaries are generated and may contain mistakes; the official description above is the record.
