# CVE-2026-120323: samanhappy MCPHub passthroughHeaders.ts information disclosure


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 2 Nov 2026
- **Updated:** 2 Nov 2026
- **Also known as:** GHSA-c48q-fjwh-j7gg

## What is CVE-2026-120323?

CVE-2026-120323 is a medium-severity vulnerability in samanhappy MCPHub, published on 2 Nov 2026. 

### Official description

A security flaw has been discovered in samanhappy MCPHub up to 1.0.45/1.1.7. Impacted is an unknown function of the file src/utils/passthroughHeaders.ts. The manipulation of the argument passthroughHeaders results in information disclosure. The attack may be launched remotely. Upgrading to version 1.1.8 is recommended to address this issue. The patch is identified as 040f7b9ae004070bdfe5084cde6bc2c609f78e76. It is advisable to upgrade the affected component.

Weakness: CWE-284 (Improper Access Control), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

No fix has been published for CVE-2026-120323 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-120323 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-120323 is a medium-severity vulnerability in samanhappy MCPHub, published on 2 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-120323 exists.

Affected product: samanhappy MCPHub. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-120323/ (Markdown: https://insights.sbomify.com/CVE-2026-120323/index.md)
```

## Sources

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

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