Summary
9router has an Incomplete Fix: Local-Only Access Gate Bypass in 9router via Host Header SpoofING
Impact
An attacker who can reach a proxied/tunneled 9router instance and obtain the deterministic CLI token can bypass the local-only restriction and interact with MCP child processes (node, python, npx, etc.) via stdin. This achieves the same impact as CVE-2026-46339: remote code execution on the host.
The severity is reduced from CVE-2026-46339's CVSS 10.0 because:
- Requires proxied/tunneled deployment (not default localhost-only)
- Requires obtaining the CLI token (deterministic but not trivially guessable without another primitive)
CVE-2026-49353 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. No fixed version is listed yet, so configuration controls and monitoring matter more in the interim.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Check actual source IP, not headers. Use
request.ip,request.socket.remoteAddress, or a trustedX-Forwarded-Forheader with known proxy configuration instead ofHost/Originfor the local-only gate.Make CLI token non-deterministic. Generate a random token on first run and persist it, rather than deriving from machine ID. Machine IDs are often predictable or discoverable on cloud infrastructure.
Bind MCP routes to loopback at the network layer. If MCP is local-only by design, the server should bind those routes to
127.0.0.1only, not rely on middleware header checks.
Frequently Asked Questions
- What is CVE-2026-49353? CVE-2026-49353 is a high-severity security vulnerability in 9router (npm), affecting versions <= 0.4.55. No fixed version is listed yet.
- How severe is CVE-2026-49353? CVE-2026-49353 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of 9router are affected by CVE-2026-49353? 9router (npm) versions <= 0.4.55 is affected.
- Is there a fix for CVE-2026-49353? No fixed version is listed for CVE-2026-49353 yet. Monitor the advisory for updates and apply mitigations in the interim.
- Is CVE-2026-49353 exploitable, and should I be worried? Whether CVE-2026-49353 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-49353 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.