CVE-2026-79749

HIGHPre-NVD 7.67.6
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 7.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (39th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated

Also known asEUVD-2026-68685 (ENISA EUVD)Source: ENISA EUVD

7.6EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.6Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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
7.6
EG Score
7.6HIGHmedium confidence
EG Risk
50
EG Risk 50/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity76% × 45%
Impact severity (EG Severity): CVSS 7.6 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
39th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.6): severity, escalated by confirmed exploitation. This CVE's 7.6 is its impact severity (EG Severity), not escalated.

EG Severity
7.6 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-11). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

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 pull request 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 advisoryMentions a patch (unverified)

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 7× in last 7d / 30× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 119 rows on record for this CVE, as 98 entries (2 repeats merged).

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 2 repeat rows among the latest 100 are merged into the row they repeat. The 19 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.4% · 39th percentile
  2. 2026-11-11 20:56 UTCEchelonGraph re-scored
  3. 2026-11-11 16:40 UTCEPSS rescoreEPSS 0.4% · 39th percentile
  4. 2026-11-10 16:45 UTCEPSS rescoreEPSS 0.4% · 39th percentile
  5. 2026-11-09 16:36 UTCEPSS rescoreEPSS 0.4% · 39th percentile
  6. 2026-11-08 16:41 UTCEPSS rescoreEPSS 0.4% · 39th percentile
  7. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.4% · 39th percentile
  8. 2026-11-06 16:39 UTCEPSS rescoreEPSS 0.4% · 39th percentile
  9. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.4% · 39th percentile
  10. 2026-11-04 16:36 UTCEPSS rescoreEPSS 0.4% · 39th percentile
  11. 2026-11-04 13:50 UTCEchelonGraph re-scored
  12. 2026-11-03 16:49 UTCEPSS rescoreEPSS 0.4% · 39th percentile
  13. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.4% · 39th percentile
  14. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.4% · 39th percentile
  15. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.4% · 39th percentile
  16. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.4% · 39th percentile
  17. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  18. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  19. 2026-10-28 07:13 UTCEchelonGraph re-scored
  20. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  21. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  22. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  23. 2026-10-25 13:59 UTCEchelonGraph re-scored
  24. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  25. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.4% · 38th percentile
Show 73 more
  1. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  2. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  3. 2026-10-20 18:16 UTCEchelonGraph re-scored
  4. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  5. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  6. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  7. 2026-10-18 03:10 UTCEchelonGraph re-scored
  8. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  9. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  10. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  11. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  12. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  13. 2026-10-13 06:37 UTCEchelonGraph re-scored
  14. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  15. 2026-10-12 14:58 UTCEchelonGraph re-scored
  16. 2026-10-11 19:22 UTCEchelonGraph re-scored
  17. 2026-10-11 16:38 UTCEchelonGraph re-scored
  18. 2026-10-11 13:56 UTCEchelonGraph re-scored
  19. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  20. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  21. 2026-10-10 00:29 UTCEchelonGraph re-scored
  22. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  23. 2026-10-09 02:21 UTCEchelonGraph re-scored
  24. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  25. 2026-10-08 00:31 UTCEchelonGraph re-scored
  26. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  27. 2026-10-06 20:26 UTCEchelonGraph re-scored
  28. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  29. 2026-10-06 07:24 UTCEchelonGraph re-scored
  30. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  31. 2026-10-05 03:31 UTCEchelonGraph re-scored
  32. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  33. 2026-10-04 02:06 UTCEchelonGraph re-scored
  34. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  35. 2026-10-02 22:24 UTCEchelonGraph re-scored
  36. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  37. 2026-10-01 21:02 UTCEchelonGraph re-scored
  38. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  39. 2026-09-30 19:41 UTCEchelonGraph re-scored
  40. 2026-09-30 03:38 UTCEchelonGraph re-scored
  41. 2026-09-29 15:24 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  42. 2026-09-28 23:05 UTCEchelonGraph re-scored
  43. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  44. 2026-09-27 21:41 UTCEchelonGraph re-scored
  45. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  46. 2026-09-26 20:20 UTCEchelonGraph re-scored
  47. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  48. 2026-09-26 07:11 UTCEchelonGraph re-scored
  49. 2026-09-26 00:28 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  50. 2026-09-24 22:03 UTCEchelonGraph re-scored
  51. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  52. 2026-09-23 20:01 UTCEchelonGraph re-scored
  53. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  54. 2026-09-22 18:41 UTCEchelonGraph re-scored
  55. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  56. 2026-09-22 05:54 UTCEchelonGraph re-scored
  57. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  58. 2026-09-21 04:10 UTCEchelonGraph re-scored
  59. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  60. 2026-09-20 02:49 UTCEchelonGraph re-scored
  61. 2026-09-19 01:19 UTCEchelonGraph re-scored
  62. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  63. 2026-09-17 23:58 UTCEchelonGraph re-scored
  64. 2026-09-16 21:48 UTCEchelonGraph re-scored
  65. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  66. 2026-09-16 09:08 UTCEchelonGraph re-scored
  67. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  68. 2026-09-15 07:22 UTCEchelonGraph re-scored
  69. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  70. 2026-09-14 05:08 UTCEchelonGraph re-scored
  71. 2026-09-12 15:07 UTCEchelonGraph re-scored
  72. 2026-09-12 02:27 UTCEchelonGraph re-scored
  73. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.3% · 17th percentile

Frequently asked(5)

What is CVE-2026-79749?
CVE-2026-79749 is a high-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-79749 published?
The CVE record for CVE-2026-79749 was published on August 31, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 8, 2026; the record at its source may have been updated since.
Is CVE-2026-79749 actively exploited?
CVE-2026-79749 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (39th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-79749?
CVE-2026-79749 has a CVSS base score of 7.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-79749?
A fix for CVE-2026-79749 is available: update to the fixed version the vendor names in its advisory.

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.