CVE-2026-79749

HIGHPre-NVD 7.67.6
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 82% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
7.6EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.6Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.6
EG Score
7.6(medium)
EG Risk
50(Track*)
EG Risk 50/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity76% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
18%
KEV
Not listed

Published

August 31, 2026

Last Modified

September 8, 2026

Advisory Details (4)

Auto-updated Aug 31, 2026
Patch available. Sources: github, github_pr, github_commit, github_release.
github_release Patch Available

v1.0.32

Patch available: samanhappy/mcphub v1.0.32

https://github.com/samanhappy/mcphub/releases/tag/v1.0.32
github_commit Patch Available

commit 2b10ae36112c (samanhappy/mcphub)

Patch available: samanhappy/mcphub v1.0.31 (contains commit 2b10ae36112c)

https://github.com/samanhappy/mcphub/commit/2b10ae36112ce68deebf910b22505d44efcef552
github_pr Patch Available

fix(security): close open security advisory findings (SSRF, authz, OAuth PKCE)

Patch available: samanhappy/mcphub v1.0.32 (PR #1069 merged 2026-08-23)

https://github.com/samanhappy/mcphub/pull/1069
github Patch Available

SSRF Guard Bypass via IPv6 Transition Addresses in URL Validation · Advisory · samanhappy/mcphub · GitHub

https://github.com/samanhappy/mcphub/security/advisories/GHSA-pr4x-3pc7-2fhw

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 13× in last 7d / 37× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-21 04:10 UTCEG score recompute
  2. 2026-09-20 20:16 UTCEPSS rescore
  3. 2026-09-20 02:49 UTCEG score recompute
  4. 2026-09-19 01:19 UTCEG score recompute
  5. 2026-09-18 19:28 UTCEPSS rescore
  6. 2026-09-17 23:58 UTCEG score recompute
  7. 2026-09-16 21:48 UTCEG score recompute
  8. 2026-09-16 14:08 UTCEPSS rescore
  9. 2026-09-16 09:08 UTCEG score recompute
  10. 2026-09-16 05:15 UTCEPSS rescore
  11. 2026-09-15 07:22 UTCEG score recompute
  12. 2026-09-15 03:12 UTCEPSS rescore
  13. 2026-09-15 03:12 UTCEPSS rescore
  14. 2026-09-14 05:08 UTCEG score recompute
  15. 2026-09-12 15:07 UTCEG score recompute
  16. 2026-09-12 02:27 UTCEG score recompute
  17. 2026-09-11 14:53 UTCEPSS rescore
  18. 2026-09-11 14:53 UTCEPSS rescore
  19. 2026-09-11 13:46 UTCEG score recompute
  20. 2026-09-10 12:24 UTCEG score recompute
  21. 2026-09-09 09:52 UTCEG score recompute
  22. 2026-09-08 22:01 UTCEPSS rescore
  23. 2026-09-07 16:34 UTCEG score recompute
  24. 2026-09-06 15:13 UTCEG score recompute
  25. 2026-09-06 13:48 UTCEPSS rescore
Show 12 more
  1. 2026-09-06 02:31 UTCEG score recompute
  2. 2026-09-05 01:08 UTCEG score recompute
  3. 2026-09-02 22:17 UTCEG score recompute
  4. 2026-09-02 14:12 UTCEPSS rescore
  5. 2026-09-01 20:53 UTCEG score recompute
  6. 2026-09-01 13:54 UTCEPSS rescore
  7. 2026-09-01 08:13 UTCEG score recompute
  8. 2026-08-31 19:28 UTCEG score recompute
  9. 2026-08-31 18:55 UTCEG score recompute
  10. 2026-08-31 18:25 UTCEG score recompute
  11. 2026-08-31 18:02 UTCEG score recompute
  12. 2026-08-31 17:59 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-79749?
CVE-2026-79749 is a high vulnerability published on August 31, 2026. 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,…
When was CVE-2026-79749 disclosed?
CVE-2026-79749 was first published in the National Vulnerability Database on August 31, 2026, with the most recent update on September 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-79749 actively exploited?
CVE-2026-79749 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 82.2% of all scored CVEs.
What is the CVSS score of CVE-2026-79749?
CVE-2026-79749 has a CVSS v3 base score of 7.6 (NVD).
How do I remediate CVE-2026-79749?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-79749, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-79749

Explore →

Is Your Infrastructure Affected by CVE-2026-79749?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.