MCPHub has Path Traversal via Malicious MCPB Manifest Name

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

7.2 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2026-79743: 0.54% estimated exploitation activity in the next 30 days; percentile 45.29 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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. 1. Summary - Vulnerability Type: Path Traversal (CWE-22) - Sink Location: src/controllers/mcpbController.ts:107 - Vulnerability Description: The name field from an uploaded MCPB manifest is used directly, without sanitization or normalization, to construct a file system path for directory creation and move operations, which may lead to path traversal attacks. 2. Analysis Logic Step 1: Inspect the identified sink…

Published by the source

22 Apr 2026, 20:50 UTC

Last modified by the source

1 Sep 2026, 03:55 UTC

Source last checked

26 Oct 2026, 12:51 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-p3h2-2j4p-p83g

2. Revision 2 · amended · 25 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-p3h2-2j4p-p83g

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-79743

Advisory: MCPHub has Path Traversal via Malicious MCPB Manifest Name
IDs: CVE-2026-79743, GHSA-p3h2-2j4p-p83g
Record: https://patchnext.com/advisories/cve-2026-79743 (revision 3, source checked 26 Oct 2026, 12:51 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @samanhappy/mcphub 0.12.13. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @samanhappy/mcphub: affected < 0.12.13; fixed in 0.12.13

## Suggested inspection (read-only)
- `npm ls @samanhappy/mcphub --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @samanhappy/mcphub.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-p3h2-2j4p-p83g (OSV record GHSA-p3h2-2j4p-p83g lists affected ranges: npm @samanhappy/mcphub >=0 <0.12.13 (fixed))
- Verified: https://github.com/advisories/GHSA-p3h2-2j4p-p83g (GitHub-reviewed advisory GHSA-p3h2-2j4p-p83g lists affected ranges: npm @samanhappy/mcphub >=0 <0.12.13)

Commands are suggestions: review each one before running it.