Vulnerabilities in pkg:npm/@jshookmcp/jshook
PACKAGECVE-2026-49856 is a MODERATE (CVSS 4.3) icmp probe and traceroute skip vulnerability (CWE-918: Server-Side Request Forgery (SSRF)) affecting @jshookmcp/jshook libraries in the npm ecosystem. The issue involves icmp probe and traceroute skip local-network ssrf authorization. Remediation is available by upgrading affected packages to version 0.3.2.
pkg:npm/@jshookmcp/jshook
Vulnerability advisories affecting package pkg:npm/@jshookmcp/jshook. Select an advisory below to view technical details or fixes.
| Advisory ID | CVE / NVD | Severity | Summary |
|---|---|---|---|
| GHSA-c5r6-m4mr-8q5j | CVE-2026-49856 | MODERATE | @jshookmcp/jshook: ICMP probe and traceroute skip local-network SSRF authorization |
CVE-2026-49856 at a Glance
Security Impact
CVSS: 4.3
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N).
How to Fix CVE-2026-49856
To remediate this vulnerability, upgrade all affected @jshookmcp/jshook dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
npm install @jshookmcp/jshook@0.3.2
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
npm ls @jshookmcp/jshook
How to Check if You Are Affected
To determine whether your Node.js application is affected by CVE-2026-49856, inspect your project dependencies using npm:
npm ls @jshookmcp/jshook
Analyze the terminal output to locate any version of @jshookmcp/jshook in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.3.2), your application is affected.
Note: The npm ls @jshookmcp/jshook command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-918: Server-Side Request Forgery (SSRF), where the web server receives a url or similar request from an upstream component and retrieves the contents of this url, but it does not sufficiently ensure that the request is being sent to the expected destination. In @jshookmcp/jshook, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-49856 Affected @jshookmcp/jshook Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
@jshookmcp/jshook
|
npm |
≥ 0.3.1
< 0.3.2
All 1 versions
0.3.1
|
0.3.2
|
References
Frequently Asked Questions
What is CVE-2026-49856?
Which @jshookmcp/jshook versions are affected?
What version fixes CVE-2026-49856?
Is @jshookmcp/jshook affected?
What is the CVSS score of CVE-2026-49856?
What CWE is associated with CVE-2026-49856?
How can I check npm dependencies for CVE-2026-49856?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-c5r6-m4mr-8q5j",
"modified" : "2026-07-01T18:14:57Z",
"published" : "2026-07-01T18:14:57Z",
"aliases" : [ "CVE-2026-49856" ],
"summary" : "@jshookmcp/jshook: ICMP probe and traceroute skip local-network SSRF authorization",
"details" : "## Summary\n\nThe 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.\n\nAn MCP client with access to an active network domain can therefore ask the jshookmcp server to probe internal addresses such as 10.0.0.1 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.\n\n## Affected code\n\nCurrent main https://github.com/vmoranv/jshookmcp/commit/d309c395738638e384c28c0f599b47b2213ab595 and npm package @jshookmcp/jshook 0.3.1 both contain the issue.\n\n- src/server/domains/network/handlers/raw-latency-handlers.ts:61-66: network_rtt_measure parses optional authorization and calls resolveAuthorizedTransportTarget before probing.\n- src/server/domains/network/handlers/raw-latency-handlers.ts:185-190: network_latency_stats uses the same authorization guard.\n- src/server/domains/network/handlers/raw-latency-handlers.ts:123-139: network_traceroute resolves target with resolveHostname and calls traceroute without an authorization policy check.\n- src/server/domains/network/handlers/raw-latency-handlers.ts:240-257: network_icmp_probe resolves target with resolveHostname and calls icmpProbe without an authorization policy check.\n- src/server/domains/network/handlers/raw-latency-handlers.ts:408-416: resolveHostname returns IPv4 literals directly and otherwise performs DNS A lookup without checking private, loopback, link-local, or reserved ranges.\n- src/utils/network/ssrf-policy.ts:244-316: the central policy blocks private targets unless explicit authorization or ALLOW_LOCAL_SSRF=true is set.\n\n## Reproduction\n\nUsed a focused regression test against the real handleCallTool and RawHandlers call path with fake native ICMP and policy sinks. The test does not send external traffic. It proves the denied control and the bypass through the same MCP meta-tool dispatch path.\n\nTest file path in my local checkout:\n\n```text\ntests/server/security/jshookmcp-network-meta-boundary.test.ts\n```\n\nRelevant test body:\n\n```ts\nit('denied control: RTT path consults the SSRF authorization guard for private targets', async () => {\n const handler = new RawHandlers();\n state.resolveAuthorizedTransportTarget.mockRejectedValue(new Error('RTT measurement blocked: target resolves to a private or reserved address.'));\n await expect(handler.handleNetworkRttMeasure({ url: 'https://10.0.0.1/', probeType: 'tcp' })).rejects.toThrow(/blocked/);\n expect(state.resolveAuthorizedTransportTarget).toHaveBeenCalled();\n expect(state.icmpProbe).not.toHaveBeenCalled();\n});\n\nit('bypass proof: call_tool can drive network_icmp_probe to a private IP without the SSRF authorization guard', async () => {\n const raw = new RawHandlers();\n const ctx = {\n router: { has: vi.fn((name: string) => name === 'network_icmp_probe') },\n executeToolWithTracking: vi.fn((name: string, args: Record<string, unknown>) => raw.handleNetworkIcmpProbe(args)),\n } as any;\n\n const response = await handleCallTool(ctx, { name: 'network_icmp_probe', args: { target: '10.0.0.1', ttl: 64 } });\n const body = JSON.parse(response.content[0].text);\n\n expect(body.success).toBe(true);\n expect(ctx.router.has).toHaveBeenCalledWith('network_icmp_probe');\n expect(ctx.executeToolWithTracking).toHaveBeenCalledWith('network_icmp_probe', { target: '10.0.0.1', ttl: 64 });\n expect(state.resolveAuthorizedTransportTarget).not.toHaveBeenCalled();\n expect(state.icmpProbe).toHaveBeenCalledWith(expect.objectContaining({ target: '10.0.0.1', ttl: 64 }));\n});\n```\n\nCommand run:\n\n```bash\ncorepack pnpm exec vitest run --config vitest.config.ts tests/server/security/jshookmcp-network-meta-boundary.test.ts --reporter=verbose\n```\n\nResult:\n\n```text\nTest Files 1 passed (1)\nTests 4 passed (4)\n```\n\nThe observed vulnerable call sequence is:\n\n```text\ncall_tool(name=network_icmp_probe, args={target: 10.0.0.1, ttl: 64})\n -> ctx.router.has(network_icmp_probe) == true\n -> ctx.executeToolWithTracking(network_icmp_probe, validatedArgs)\n -> RawHandlers.handleNetworkIcmpProbe(validatedArgs)\n -> resolveHostname(10.0.0.1) returns 10.0.0.1\n -> icmpProbe({ target: 10.0.0.1, ttl: 64, ... })\n```\n\nresolveAuthorizedTransportTarget is not called on this path. The same missing policy pattern exists for network_traceroute.\n\n## Impact\n\nAn MCP client with access to the active network domain can use the server as a backend-origin internal network probing oracle. The result can reveal whether internal hosts respond, approximate latency, traceroute hops, and ICMP error classes from the server network position.\n\nThe practical impact is strongest when jshookmcp is exposed over Streamable HTTP or another remote transport, multiple clients share one server, or the server runs on Windows or with raw socket capability. This is not code execution and does not by itself exfiltrate response bodies.\n\n## Remediation\n\nApply the same authorization model used by network_rtt_measure and network_latency_stats to network_icmp_probe and network_traceroute. In particular, accept an optional authorization object, resolve the target through the central policy helper or an equivalent host-only policy helper, block private and reserved ranges by default, and pass only the policy-approved resolved address to the native probe. Add regression tests for default-denied private targets, authorized private CIDR access, private hostnames, and call_tool dispatch.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "npm",
"name" : "@jshookmcp/jshook"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0.3.1"
}, {
"fixed" : "0.3.2"
} ]
} ],
"versions" : [ "0.3.1" ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/vmoranv/jshookmcp/security/advisories/GHSA-c5r6-m4mr-8q5j"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/vmoranv/jshookmcp"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-918" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2026-07-01T18:14:57Z",
"nvd_published_at" : null
}
}