{"answers":{"affected":"2 open source packages ship an affected version, including @jshookmcp/jshook.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-49856 exists.","fix":"Upgrade @jshookmcp/jshook to 0.3.2 or later.","what":"CVE-2026-49856 is a medium-severity server-side request forgery vulnerability in vmoranv jshookmcp, published on 13 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-49856 and fix it if it is affected.\n\nWhat it is: CVE-2026-49856 is a medium-severity server-side request forgery vulnerability in vmoranv jshookmcp, published on 13 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-49856 exists.\n\nAffected packages and fixed versions:\n- @jshookmcp/jshook (npm): affected from 0.3.1; fixed in 0.3.2\n- @jshookmcp/jshook (npm): affected from 0.3.1; fixed in 0.3.2\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-49856/ (Markdown: https://insights.sbomify.com/CVE-2026-49856/index.md)","id":"CVE-2026-49856","markdown":"https://insights.sbomify.com/CVE-2026-49856/index.md","name":"CVE-2026-49856","record":{"aliases":["GHSA-c5r6-m4mr-8q5j"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"MCP server library","requires_auth":"low_privilege","summary":"Attackers can bypass SSRF protections in the jshook MCP server to probe internal network addresses via ICMP and traceroute tools.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"@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.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"@jshookmcp/jshook: ICMP probe and traceroute skip local-network SSRF authorization","id":"CVE-2026-49856","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"auth-fetch-mcp has SSRF Protection Bypass via IPv4-mapped IPv6 Loopback","id":"CVE-2026-49857"},"packages":[{"ecosystem":"npm","fixed":["0.3.2"],"introduced":["0.3.1"],"last_affected":[],"package":"@jshookmcp/jshook","purl":null,"source":"GHSA-c5r6-m4mr-8q5j"},{"ecosystem":"npm","fixed":["0.3.2"],"introduced":["0.3.1"],"last_affected":[],"package":"@jshookmcp/jshook","purl":"pkg:npm/%40jshookmcp/jshook","source":"GHSA-c5r6-m4mr-8q5j"}],"prev":{"headline":"tornado AsyncHTTPClient accumulates decompressed chunks without size limit (gzip bomb)","id":"CVE-2026-49855"},"products":["jshookmcp"],"published":"2026-08-13","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-13","vendors":["vmoranv"]},"summary":"Attackers can bypass SSRF protections in the jshook MCP server to probe internal network addresses via ICMP and traceroute tools.","url":"https://insights.sbomify.com/CVE-2026-49856/"}