Quick answers
- Is CVE-2026-79750 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-79750 being exploited in the wild.
- How severe is CVE-2026-79750?
- High severity, with a CVSS score of 7.7, published 31 August 2026.
- Which products and versions are affected?
- Samanhappy Mcphub <= 1.0.29.
- Is there a fix for CVE-2026-79750?
- A patch was published on 2026-08-20: Version 1.0.30 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-79750 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-79750?
- 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.
Technical details
This is a horizontal privilege escalation (IDOR) vulnerability in MCPHub's tool-execution API. The vulnerability stems from an incomplete authorization check: while list views and configuration routes enforce server ownership via canAccessServer() and filterData(), the POST /api/tools/:serverName/:toolName execution endpoint resolves servers globally via getServerByName() without any ownership or admin check. An authenticated non-admin user can directly call this endpoint with any server name they discover (including through error messages or enumeration) to invoke tools. The attack vector is network-reachable, requires only a valid non-admin account (which an insider or tenant of a multi-tenant deployment would have), and requires no user interaction. PoC demonstrates arbitrary file read (/etc/passwd, user secrets) and SSRF attacks. The fix is to apply the existing ownership gate (canAccessServer) to the execution routes, either during server resolution or as a pre-execution check. Version 1.0.30 patches this by implementing group visibility and shared user functionality.
Affected products
- samanhappy MCPHub <= 1.0.29
Timeline
- 2026-08-23: disclosed
- 2026-08-20: patched: Version 1.0.30 released