CVE-2026-79748: MCPHub: Authenticated non-admin user achieves RCE via POST /api/servers (missing authorization on stdio command/args)
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 0.12.15, the POST /api/servers and PUT /api/servers/:name endpoints in MCPHub create/update MCP server configurations and then immediately spawn the configured stdio process via child_process.spawn. Authentication is required, but there is no authorization check restricting these endpoints to admins, and there is no allowlist/sanitization on the command and args fields. As a result, any authenticated non-admin user can submit a server configuration with command:"/bin/sh" (or any other binary) and arbitrary args, causing MCPHub to execute the attacker-controlled process as the MCPHub server's OS user (commonly root in the published Docker image and in npx/systemd deployments). This issue has been patched in version 0.12.15.
Security readout for executives and security teams
Plain-English summary
MCPHub versions before 0.12.15 let any signed-in user, including non-administrators, configure a process that the server immediately runs. A compromised or low-privilege account could therefore take control of the MCPHub host, access sensitive data, alter services, or cause outages with the permissions of the MCPHub operating-system account.
Executive priority
Treat as an immediate remediation priority for internet-accessible, multi-user, or privileged MCPHub deployments. Upgrade promptly, restrict administrative APIs, and investigate unexpected configuration changes. The absence of confirmed active exploitation lowers certainty about current attacks, not the potential business impact.
Technical view
POST /api/servers and PUT /api/servers/:name require authentication but lack administrator authorization. They accept unrestricted stdio command and argument fields, then invoke child_process.spawn. This CWE-862 authorization failure enables remote code execution as MCPHub’s OS user. The supplied sources identify version 0.12.15 as patched.
Likely exposure
Exposure exists where MCPHub earlier than 0.12.15 is deployed and untrusted, compromised, or insufficiently privileged accounts can authenticate to its API. Impact is especially severe when MCPHub runs as root, which the source bundle says is common in published Docker, npx, and systemd deployments.
Exploitation context
The attack requires an authenticated account but no administrator privileges or user interaction. Network reachability to the affected API is also necessary. The supplied record is not in CISA KEV, and the provided sources do not establish active exploitation in the wild.
Researcher notes
CVSS 3.1 is 9.9: network-accessible, low complexity, low privileges, no interaction, changed scope, and high confidentiality, integrity, and availability impact. Assessment is limited to the supplied public record, GitHub advisory, patch pull request, and release information; no independent exploitation evidence was provided.
Mitigation direction
Upgrade MCPHub to version 0.12.15 or later.
Restrict server-configuration endpoints to trusted administrators until upgrading.
Run MCPHub with the least operating-system privileges required.
Review vendor guidance and release notes before returning restricted access.
Validation and detection
Inventory MCPHub instances and confirm every installed version.
Verify non-administrator accounts cannot create or update server configurations.
Review server configurations and available operational records for unexpected changes or process launches.
Confirm the MCPHub process does not run as root unless strictly necessary.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-862: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
4Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-862 · source CWE mapping
Missing Authorization
Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.