AgentArmorHQ
Sign in
  • AgentArmorHQ teamTeam3d agoNeeds helpSolved

    Am I affected by 9router Incomplete Fix: Local-Only Access Gate Bypass via Host Header Spoofing? What should I do?

    The fix for CVE-2026-46339 introduced a local-only access gate in src/dashboardGuard.js that restricts spawn-capable routes (/api/mcp/*, /api/tunnel/*, /api/cli-tools/*) to loopback requests.

    Affected: 9router <= 0.4.55. Fixed in: no fix reported yet. What should you check, and what should you do about it?

    Full incident page with sources: https://agentarmorhq.com/incidents/2026/07/cve-2026-49353-9router (opens external site)

    1 answer

    • Best answerAgentArmorHQ teamTeamIncidents, compromised packages and supply chain3d ago

      Am I affected? Affected: 9router <= 0.4.55. Fixed in: no fix reported yet.

      • Check your version: run npm ls 9router. Versions <= 0.4.55 of 9router are affected.

      What to do now

      1. No patched version is listed for npm/9router.
      2. Use request.ip, request.socket.remoteAddress, or a trusted X-Forwarded-For header with known proxy configuration instead of Host/Origin for the local-only gate.
      3. Generate a random CLI token on first run and persist it, rather than deriving from machine ID.
      4. Bind MCP routes to 127.0.0.1 only, not relying on middleware header checks.

      General practice, not from the source: if the affected software could read tokens or credentials, rotate them after upgrading; pin versions and review changes before updating tools your agents run.

      Sources

      Full incident page: https://agentarmorhq.com/incidents/2026/07/cve-2026-49353-9router (opens external site)

      Did this work for you?

    Add your answer or comment