CVE-2026-79743

MEDIUMPre-NVD 6.96.9
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 6.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (45th 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-68691 (ENISA EUVD)Source: ENISA EUVD

6.9EG
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.5%CVSS: 6.9Exploit: 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 0.12.13, MCPB File Upload Handler extracts a ZIP file and reads manifest.json from it. The name field in the manifest is directly concatenated into a file path (line 107) without any sanitization or path traversal character validation. An attacker can craft a malicious MCPB file where manifest.name is set to something like ../../../etc/malicious, causing the file to be extracted to an arbitrary location on the file system. The cleanupOldMcpbServer function (line 110) also uses the unsanitized name, potentially allowing deletion of arbitrary directories. This issue has been patched in version 0.12.13.

CVSS v3
6.9
EG Score
6.9MEDIUMmedium confidence
EG Risk
62
EG Risk 62/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)
Severity69% × 45%
Impact severity (EG Severity): CVSS 6.9 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.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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.5%
EPSS %ILE
45th
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 (6.9): severity, escalated by confirmed exploitation. This CVE's 6.9 is its impact severity (EG Severity), not escalated.

EG Severity
6.9 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). 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 or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days 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 or medium mission impact; Attend at high (mission-essential systems).

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 yes (CISA Vulnrichment) · Technical impact partial (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; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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 (3)

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

v0.12.13

Patch available: samanhappy/mcphub v0.12.13

https://github.com/samanhappy/mcphub/releases/tag/v0.12.13
GitHub pull request Patch Available

fix: harden auth and ownership checks

Patch available: samanhappy/mcphub v1.0.4 (PR #770 merged 2026-04-28)

https://github.com/samanhappy/mcphub/pull/770
GitHub advisoryMentions a patch (unverified)

Path Traversal via Malicious MCPB Manifest Name · Advisory · samanhappy/mcphub · GitHub

https://github.com/samanhappy/mcphub/security/advisories/GHSA-p3h2-2j4p-p83g

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
@samanhappy/mcphub—
  • every version up to 0.12.13: fixed in 0.12.13
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 44× 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 it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 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). Most recent first.

Showing the most recent 98 of 99 refreshes on record for this CVE.

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 1 oldest row on record is not shown and was not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-79743?
CVE-2026-79743 is a medium-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 0.12.13, MCPB File Upload Handler extracts a ZIP file and reads manifest.json from it. The name field in the manifest is…
When was the CVE record for CVE-2026-79743 published?
The CVE record for CVE-2026-79743 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-79743 actively exploited?
CVE-2026-79743 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (45th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-79743?
CVE-2026-79743 has a CVSS base score of 6.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-79743?
A fix for CVE-2026-79743 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-79743

Explore →

Is Your Infrastructure Affected by CVE-2026-79743?

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