Skip to content

AAK-MCP-JSHOOK-CVE-2026-49856-001: @jshookmcp/jshook 0.3.1 (ICMP/traceroute tools bypass the SSRF authorization policy)

Severity
MEDIUM
Category
Supply Chain (supply-chain)
Scanner
agent_audit_kit/scanners/mcp_cve_pins_2026_07.py
Auto-fixable
No.
SARIF name
JshookIcmpSsrfPolicyBypass

What it detects

@jshookmcp/jshook, an MCP server exposing JavaScript-analysis and security-research tools to agents, at 0.3.1 enforces its central SSRF authorization policy — which blocks private, loopback, link-local and reserved targets unless an authorization object explicitly permits private network access — only on the raw HTTP / TCP / TLS round-trip tools. The ICMP probe and traceroute tools resolve the caller's target and invoke the native ICMP / traceroute sink directly, skipping the policy. An MCP client holding an active network domain can therefore probe internal addresses even with local SSRF access disabled for every other raw network tool, yielding an internal reachability and route-mapping primitive from the server's network position (CVE-2026-49856, CVSS 4.3). Fixed in 0.3.2; GHSA-c5r6-m4mr-8q5j records 0.3.1 as the only affected release.

How to fix

Upgrade @jshookmcp/jshook to >= 0.3.2 and pin it. Route every network tool, including ICMP and traceroute, through the same SSRF authorization policy rather than gating only the raw HTTP/TCP/TLS paths.

To confirm the finding is gone, report only this rule:

agent-audit-kit scan . --rules AAK-MCP-JSHOOK-CVE-2026-49856-001

Limitations

Reads @jshookmcp/jshook in requirements*.txt at any depth and, at the project root only, in pyproject.toml, Pipfile, package.json, .mcp.json, mcp.json, claude_desktop_config.json and the Pipfile.lock, poetry.lock, uv.lock, package-lock.json, pnpm-lock.yaml and yarn.lock lockfiles, taking the lowest version a range allows and reporting a reference that states no version. The dependency is not read when it is declared in a sub-directory manifest (packages/app/package.json), in .cursor/mcp.json or .vscode/mcp.json, or in a lockfile format the reader does not parse (a Yarn 2+ yarn.lock). A file over 2 MB, or a lockfile over 32 MiB, is not read. A declaration nested more than 64 levels deep in package.json, a TOML manifest or an MCP config (an MCP server more than 62) is still judged, and reported without a line; a lockfile entry keeps its line at any depth.

References

  • CVE: CVE-2026-49856
  • OWASP MCP Top 10: MCP04:2025 (Software Supply Chain Attacks & Dependency Tampering), MCP05:2025 (Command Injection & Execution)
  • OWASP Agentic Top 10: ASI02 (Tool Misuse and Exploitation), ASI04 (Agentic Supply Chain Vulnerabilities)
  • Adversa AI MCP Top 25 (AAK-defined ids): ADV-SSRF-01 (Internal Network MCP)

All rules. This page is generated from the rule registry when the documentation is built; to change it, change the rule in agent_audit_kit/rules/builtin.py. To give the rule a hand-written write-up, add docs/rules/AAK-MCP-JSHOOK-CVE-2026-49856-001.md: the page then shows that text, with the registry reference appended under it.