CVE-2026-29023

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.

CVSS v3 7.3 HIGH

7.3^/10

CVSS v3 : HIGH

Vector :

Exploitability : 3.9 / Impact : 3.4

Attack Vector NETWORK

Attack Complexity LOW

Privileges Required NONE

User Interaction NONE

Confidentiality Impact LOW

Integrity Impact LOW

Availability Impact LOW

Scope UNCHANGED

References

Link	Resource
https://github.com/KeygraphHQ/shannon/issues/186
https://github.com/KeygraphHQ/shannon/pull/224
https://github.com/KeygraphHQ/shannon/pull/224/changes/023cc953db742602964b7826105278d15c28a420
https://www.vulncheck.com/advisories/keygraph-shannon-hard-coded-router-api-key

Configurations

No configuration.

History

11 Mar 2026, 13:53

Type	Values Removed	Values Added
Summary		(es) Keygraph Shannon contiene una clave API codificada de forma rígida en su configuración de router que, cuando el componente del router está habilitado y expuesto, permite a los atacantes de red autenticarse utilizando la clave estática públicamente conocida. Un atacante capaz de alcanzar el puerto del router puede redirigir solicitudes a través de la instancia de Shannon utilizando las credenciales de API del proveedor ascendente configurado de la víctima, lo que resulta en un uso no autorizado de la API y la posible divulgación de datos de solicitudes y respuestas redirigidas. La explotabilidad general de esta vulnerabilidad ha sido mitigada con la introducción del commit 023cc95.

09 Mar 2026, 18:16

Type	Values Removed	Values Added
New CVE

Information

Published : 2026-03-09 18:16

Updated : 2026-03-11 13:53

NVD link : CVE-2026-29023

Mitre link : CVE-2026-29023

CVE.ORG link : CVE-2026-29023

JSON object : View

Products Affected

No product.

CWE

CWE-798

Use of Hard-coded Credentials

{"id": "CVE-2026-29023", "cveTags": [], "metrics": {"cvssMetricV31": [{"type": "Primary", "source": "disclosure@vulncheck.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 7.3, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L", "integrityImpact": "LOW", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "LOW", "privilegesRequired": "NONE", "confidentialityImpact": "LOW"}, "impactScore": 3.4, "exploitabilityScore": 3.9}], "cvssMetricV40": [{"type": "Secondary", "source": "disclosure@vulncheck.com", "cvssData": {"Safety": "NOT_DEFINED", "version": "4.0", "Recovery": "NOT_DEFINED", "baseScore": 6.9, "Automatable": "NOT_DEFINED", "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "valueDensity": "NOT_DEFINED", "vectorString": "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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X", "exploitMaturity": "NOT_DEFINED", "providerUrgency": "NOT_DEFINED", "userInteraction": "NONE", "attackComplexity": "LOW", "attackRequirements": "NONE", "privilegesRequired": "NONE", "subIntegrityImpact": "NONE", "vulnIntegrityImpact": "LOW", "integrityRequirement": "NOT_DEFINED", "modifiedAttackVector": "NOT_DEFINED", "subAvailabilityImpact": "NONE", "vulnAvailabilityImpact": "LOW", "availabilityRequirement": "NOT_DEFINED", "modifiedUserInteraction": "NOT_DEFINED", "modifiedAttackComplexity": "NOT_DEFINED", "subConfidentialityImpact": "NONE", "vulnConfidentialityImpact": "LOW", "confidentialityRequirement": "NOT_DEFINED", "modifiedAttackRequirements": "NOT_DEFINED", "modifiedPrivilegesRequired": "NOT_DEFINED", "modifiedSubIntegrityImpact": "NOT_DEFINED", "modifiedVulnIntegrityImpact": "NOT_DEFINED", "vulnerabilityResponseEffort": "NOT_DEFINED", "modifiedSubAvailabilityImpact": "NOT_DEFINED", "modifiedVulnAvailabilityImpact": "NOT_DEFINED", "modifiedSubConfidentialityImpact": "NOT_DEFINED", "modifiedVulnConfidentialityImpact": "NOT_DEFINED"}}]}, "published": "2026-03-09T18:16:22.727", "references": [{"url": "https://github.com/KeygraphHQ/shannon/issues/186", "source": "disclosure@vulncheck.com"}, {"url": "https://github.com/KeygraphHQ/shannon/pull/224", "source": "disclosure@vulncheck.com"}, {"url": "https://github.com/KeygraphHQ/shannon/pull/224/changes/023cc953db742602964b7826105278d15c28a420", "source": "disclosure@vulncheck.com"}, {"url": "https://www.vulncheck.com/advisories/keygraph-shannon-hard-coded-router-api-key", "source": "disclosure@vulncheck.com"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Primary", "source": "disclosure@vulncheck.com", "description": [{"lang": "en", "value": "CWE-798"}]}], "descriptions": [{"lang": "en", "value": "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\u2019s 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."}, {"lang": "es", "value": "Keygraph Shannon contiene una clave API codificada de forma r\u00edgida en su configuraci\u00f3n de router que, cuando el componente del router est\u00e1 habilitado y expuesto, permite a los atacantes de red autenticarse utilizando la clave est\u00e1tica p\u00fablicamente conocida. Un atacante capaz de alcanzar el puerto del router puede redirigir solicitudes a trav\u00e9s de la instancia de Shannon utilizando las credenciales de API del proveedor ascendente configurado de la v\u00edctima, lo que resulta en un uso no autorizado de la API y la posible divulgaci\u00f3n de datos de solicitudes y respuestas redirigidas. La explotabilidad general de esta vulnerabilidad ha sido mitigada con la introducci\u00f3n del commit 023cc95."}], "lastModified": "2026-03-11T13:53:47.157", "sourceIdentifier": "disclosure@vulncheck.com"}