EUVD-2026-68690Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain any valid MCPHub user account
-
DeliveryAuthenticate and obtain session token
-
ExploitSend crafted PUT /api/system-config request
-
ExecutionServer skips isAdmin role check
-
PersistOverwrite system-wide MCP routing configuration
-
ImpactGain effective admin control over all managed MCP servers
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V8 - Authorization Least privilege enforcement
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires a valid authenticated session in MCPHub at any privilege level - no admin account is needed. The attacker must have network access to the MCPHub API. Beyond valid credentials to any user account and network reachability, no special configuration, enabled features, or non-default settings are required. Exploitation is limited by: (1) the requirement to hold at least one valid credential (PR:L per CVSS - unauthenticated exploitation is not possible), and (2) the target must be running MCPHub prior to version 1.0.29. There is no user interaction and no attack complexity beyond crafting a valid PUT request body. |
| Impact | CVSS 8.8 with AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H is an accurate reflection of real-world exploitability: the only barrier is possession of any valid MCPHub account, and no configuration complexity is required. The PR:L metric is the defining signal - in any multi-user MCPHub deployment, every non-admin account is a potential attack path. EPSS data is absent from available intelligence, preventing probabilistic exploitation likelihood comparison. The vulnerability is not listed in CISA KEV and no public POC has been identified, which moderates urgency somewhat. However, the simplicity of the exploit (a single crafted PUT request after login) means that even a mid-sized IT organization running MCPHub as a shared service should treat this as urgent regardless of KEV status. SSVC signals align with high technical impact and automatable exploitation once a credential is obtained. Risk is bounded by MCPHub's relatively niche deployment footprint, but for organizations using it, the blast radius is the entire MCP routing infrastructure. |
| Exploit ScenarioDerived | An attacker who has obtained any valid MCPHub account - including a freshly registered low-privilege user - authenticates to the API and issues a crafted PUT request to /api/system-config with a malicious payload. The server processes the request without inspecting the user's admin status, overwriting system-wide configuration such as MCP server routing rules or API endpoint definitions. This can redirect traffic to attacker-controlled infrastructure, disable downstream service authentication, or cause a complete disruption of MCP orchestration across the hub. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 31, 2026
Privilege escalation in MCPHub prior to version 1.0.29 allows any authenticated low-privilege user to modify system-wide configuration via the PUT /api/system-config endpoint. The handler updateSystemConfig never validates req.user.isAdmin, meaning the app-wide authentication middleware - which only confirms a valid session exists - is the sole barrier, granting any account holder effective administrative control over routing rules and server integrations. No public exploit has been identified at time of analysis, but the attack is trivially reproducible given network access and any valid credential.
RemediationAI
Upgrade to MCPHub version 1.0.29 or later, available at https://github.com/samanhappy/mcphub/releases/tag/v1.0.29 per the vendor advisory at https://github.com/samanhappy/mcphub/security/advisories/GHSA-4gc8-885f-qj36. If an immediate upgrade is not feasible, restrict the PUT /api/system-config endpoint at the reverse-proxy or WAF layer to explicitly allowlisted admin source IPs - note this has operational impact if admin users connect from dynamic or shared IPs. A secondary compensating control is to disable open user registration, reducing the pool of accounts that could be leveraged; however this does not protect against insider threats or compromised non-admin credentials. Neither workaround substitutes for patching, as they rely on external controls rather than fixing the missing authorization check in the application itself.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
MCPHub is an open-source Node.js application (github.com/samanhappy/mcphub) that acts as a centralized gateway for managing, routing, and orchestrating multiple Model Context Protocol (MCP) servers and APIs into unified endpoints. The root cause is CWE-269 (Improper Privilege Management): the PUT /api/system-config route is protected only by a global authentication middleware confirming session validity and a rate limiter, but the updateSystemConfig handler contains no role-based access control (RBAC) check. Specifically, it never reads or evaluates req.user.isAdmin, allowing any authenticated user - regardless of role - to invoke an endpoint intended exclusively for administrators. No CPE string was provided in source intelligence; the affected software is the MCPHub Node.js application across all releases prior to v1.0.29.
Know when the next one hits your stack
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Network-accessible API requiring only a valid low-privilege session with no scope change, as impact is confined to the MCPHub instance itself.
Primary rating from Vendor (github).
CVSS VectorVendor: github
Lifecycle Timeline
2DescriptionCVE.org
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 1.0.29, MCPHub's PUT /api/system-config endpoint (handler updateSystemConfig) performs no authorization check. It is protected only by the app-wide authentication middleware and a rate limiter - it never inspects req.user.isAdmin. This issue has been patched in version 1.0.29.
Technical POC Analysis
Advisory: GHSA-4gc8-885f-qj36 (samanhappy/mcphub).
Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.
Executive ViewAI
MCPHub versions prior to 1.0.29 contain a privilege escalation vulnerability allowing any authenticated user to gain administrative control over system configuration, routing rules, and server integrations. Compromised or malicious employee accounts can exploit this with a single API call to fully hijack application infrastructure without elevated privileges. Organizations using MCPHub risk unauthorized configuration changes, rogue integrations, and lateral movement to dependent systems.
No vendor-released patch identified at time of analysis. Interim mitigations: (1) Restrict network access to PUT /api/system-config via firewall or API gateway ACLs, limiting to verified admin IP ranges only; (2) Deploy WAF rules blocking PUT requests to /api/system-config from non-admin source IPs; (3) Implement real-time audit logging and alerting for all /api/system-config modification attempts; (4) Enforce multi-factor authentication (MFA) on all MCPHub user accounts to reduce credential compromise risk; (5) Isolate MCPHub instances from sensitive production systems using network segmentation.
Threat Intelligence Overview
NVD
CVE.org
EPSS
Vulnrichment
GitHub
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
Exploit-DB