# CVE-2026-79743: MCPHub: Path Traversal via Malicious MCPB Manifest Name

> Attackers can exploit unsanitized manifest names in MCPB uploads to write or delete arbitrary files on the server filesystem.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Aug 2026
- **Updated:** 31 Aug 2026
- **Also known as:** GHSA-p3h2-2j4p-p83g

## What is CVE-2026-79743?

CVE-2026-79743 is a medium-severity path traversal vulnerability in samanhappy mcphub, published on 31 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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 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.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-79743?

2 open source packages ship an affected version, including @samanhappy/mcphub.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@samanhappy/mcphub` | npm | All versions | 0.12.13 |
| `@samanhappy/mcphub` | npm | All versions | 0.12.13 |

## How do I fix CVE-2026-79743?

Upgrade @samanhappy/mcphub to 0.12.13 or later.

## Is CVE-2026-79743 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-79743 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-79743 and fix it if it is affected.

What it is: CVE-2026-79743 is a medium-severity path traversal vulnerability in samanhappy mcphub, published on 31 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-79743 exists.

Affected packages and fixed versions:
- @samanhappy/mcphub (npm): affected all versions; fixed in 0.12.13
- @samanhappy/mcphub (npm): affected all versions; fixed in 0.12.13

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-79743/ (Markdown: https://insights.sbomify.com/CVE-2026-79743/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-79743
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-79743
- OSV: https://osv.dev/vulnerability/CVE-2026-79743

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-79743/
Summaries are generated and may contain mistakes; the official description above is the record.