Quick answers
- Is CVE-2026-79749 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-79749 being exploited in the wild.
- How severe is CVE-2026-79749?
- Informational severity, published 31 August 2026.
- Which products and versions are affected?
- Samanhappy Mcphub before 1.0.32.
- Is there a fix for CVE-2026-79749?
- A patch was published on 2026-08-23: Fix merged in PR #1069 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-79749 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-79749?
- Check whether you run Samanhappy Mcphub at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
MCPHub's SSRF (Server-Side Request Forgery) guard in src/utils/ssrf.ts implements a custom isBlockedIpv6 function that is incomplete. It checks only for loopback, link-local, unique-local, IPv4-mapped, and IPv4-compatible IPv6 addresses but fails to block IPv6 transition address families: NAT64 (64:ff9b::/96 and 64:ff9b:1::/48), 6to4 (2002::/16), Teredo (2001::/32), site-local (fec0::/10), and multicast (ff00::/8). An attacker can specify an MCP server URL using these transition formats to encode private IPv4 addresses, thereby bypassing the SSRF blocklist and reaching internal infrastructure. The vulnerability is network-reachable and requires only the ability to specify a server URL. Patches are available in version 1.0.32 and later.
Affected products
- samanhappy MCPHub before 1.0.32
Timeline
- 2026-08-31: disclosed
- 2026-08-23: patched: Fix merged in PR #1069