SSRF (Server-Side Request Forgery) in @jshookmcp/jshook (CVE-2026-49856)
Summary
SSRF in @jshookmcp/jshook (CVE-2026-49856). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 0.3.2 or later.
Original description
The description as published by the source.
@jshookmcp/jshook is an MCP server that gives AI agents tools for JavaScript analysis and security research. In version 0.3.1, he network domain has a central SSRF authorization policy that blocks private, loopback, link-local, and reserved targets unless an explicit authorization object allows private network access. The policy is enforced by raw HTTP/TCP/TLS RTT tools, but the ICMP probe and traceroute tools resolve the target and invoke the native ICMP/traceroute sink directly. An MCP client with access to an active network domain can therefore ask the jshookmcp server to probe internal addresses even when local SSRF access is disabled for the other raw network tools. This exposes an internal reachability and route mapping primitive from the server network position. Version 0.3.2 fixes the issue.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-49856 has been found in @jshookmcp/jshook.
Risk of unauthorized operations or information disclosure. CVSS score: 4.3/10.
What to do: upgrade @jshookmcp/jshook to 0.3.2 or later.
If unsure, ask your IT team or search "@jshookmcp/jshook CVE-2026-49856" on the vendor's site.
CVE-2026-49856 (@jshookmcp/jshook) — CWE-918 / CVSS v3 4.3
Attack vector: remote (network-reachable) / no user interaction
Patched: 0.3.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
SSRF (CWE-918) exists in @jshookmcp/jshook.
Check the vendor advisory for the affected versions of @jshookmcp/jshook.
Severity: Medium (CVSS 4.3/10). Risk of unauthorized operations or information disclosure.
Update to 0.3.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@jshookmcp/jshook' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@jshookmcp/jshook' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@jshookmcp/jshookを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade @jshookmcp/jshook to 0.3.2ステージング環境で 0.3.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- patch github.com
- web github.com