Quick answers
- Is CVE-2026-120323 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-120323 being exploited in the wild.
- How severe is CVE-2026-120323?
- Medium severity, with a CVSS score of 4.3, published 2 November 2026.
- Which products and versions are affected?
- Samanhappy Mcphub up to 1.0.45 and 1.1.0–1.1.7.
- Is there a fix for CVE-2026-120323?
- Yes: fixed in 1.1.8. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-120323 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-120323?
- Check whether you run Samanhappy Mcphub at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 1.1.8
Technical details
The vulnerability is an information disclosure (CWE-200) in passthroughHeaders handling: MCPHub collects all request headers from the caller (including Authorization, Cookie, and X-Api-Key) and forwards them verbatim to an attacker-controlled upstream URL if they are listed in the openapi.passthroughHeaders configuration. No denylist blocks credential headers, and non-privileged users can register such configurations. Exploitation requires authentication to MCPHub (to register the server or call a tool) and user interaction (victim must invoke a tool on the malicious server), but results in credential exfiltration with no attack complexity.
Affected products
- samanhappy MCPHub up to 1.0.45 and 1.1.0–1.1.7
Timeline
- 2026-11-02: disclosed