{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-79749 exists.","fix":"No fix has been published for CVE-2026-79749 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-79749 is a high-severity server-side request forgery vulnerability in samanhappy mcphub, published on 31 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-79749 and fix it if it is affected.\n\nWhat it is: CVE-2026-79749 is a high-severity server-side request forgery vulnerability in samanhappy mcphub, published on 31 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-79749 exists.\n\nAffected product: samanhappy mcphub. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-79749/ (Markdown: https://insights.sbomify.com/CVE-2026-79749/index.md)","id":"CVE-2026-79749","markdown":"https://insights.sbomify.com/CVE-2026-79749/index.md","name":"CVE-2026-79749","record":{"aliases":["GHSA-pr4x-3pc7-2fhw"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"MCP server hub","requires_auth":"low_privilege","summary":"Attackers can bypass SSRF protections in MCPHub by using IPv6 transition addresses to access internal network resources.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.6,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"MCPHub is a unified hub for centrally managing and dynamically orchestrating multiple MCP servers/APIs into separate endpoints with flexible routing strategies. Prior to version 1.0.32, MCPHub's SSRF guard in src/utils/ssrf.ts uses a custom isBlockedIpv6 function that only checks for loopback, link-local, unique-local, IPv4-mapped, and IPv4-compatible IPv6 addresses. IPv6 transition address families -- NAT64 (64:ff9b::/96), 6to4 (2002::/16), and Teredo (2001::/32) -- are not checked. An attacker who can specify a URL for an MCP server connection can encode a private IPv4 address inside one of these IPv6 forms to bypass the SSRF guard and reach internal infrastructure. This issue has been patched in version 1.0.32.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"MCPHub: SSRF Guard Bypass via IPv6 Transition Addresses in URL Validation","id":"CVE-2026-79749","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"Missing authorization in mcphub","id":"CVE-2026-79750"},"packages":[],"prev":{"headline":"MCPHub: Authenticated non-admin user achieves RCE via POST /api/servers (missing authorization on stdio command/args)","id":"CVE-2026-79748"},"products":["mcphub"],"published":"2026-08-31","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"total"},"state":"PUBLISHED","updated":"2026-08-31","vendors":["samanhappy"]},"summary":"Attackers can bypass SSRF protections in MCPHub by using IPv6 transition addresses to access internal network resources.","url":"https://insights.sbomify.com/CVE-2026-79749/"}