MCPNews

The Model Context Protocol ecosystem, verified

Current spec 2026-07-28

Eight CVE records land at once for MCPHub, and every one of them trails a shipped fix

GitHub's CNA published eight CVE records against MCPHub, the self-hosted MCP gateway, in one batch on 2026-08-31. The worst, CVE-2026-79748, let any authenticated non-admin user reach remote code execution through the server registration endpoint; it was fixed in v0.12.15 back on 2026-05-02. The other seven cover missing authorization, SSRF and cross-tenant access, all fixed between April and 2026-08-23. The repository carries ten further advisories that have no CVE ids at all, three of them rated critical.

GitHub's CVE numbering authority published eight records against MCPHub on 2026-08-31, all reserved together on 2026-08-25. MCPHub (samanhappy/mcphub, about 2,400 stars) is a self-hosted gateway that manages multiple MCP servers behind shared endpoints, which is what makes its authorization model the whole story: seven of the eight records describe some path around it.

The critical one is CVE-2026-79748, rated 9.9. Before v0.12.15, the POST /api/servers and PUT /api/servers/:name endpoints accepted stdio server configurations, command and arguments included, from any authenticated user without an admin check, so a non-admin account could register a server whose command was an arbitrary process and have the hub spawn it. The fix shipped on 2026-05-02, almost four months before the record. The remaining seven follow the same trailing pattern: a non-admin rewrite of the global security configuration (CVE-2026-79744, fixed v1.0.29), missing role checks on prompt and resource CRUD (CVE-2026-79745), a server-scoped bearer key that unlocked a whole group on any overlap (CVE-2026-79746), SSRF through the OpenAPI proxy (CVE-2026-79747) and an IPv6-transition-address bypass of its guard (CVE-2026-79749), cross-tenant tool execution (CVE-2026-79750), and a path traversal via MCPB manifest names (CVE-2026-79743, low, fixed in April). The newest fix among them, v1.0.32, shipped on 2026-08-23, eight days before the records.

The CVE batch understates the repository's own disclosure record. The project has published 18 advisories, and the ten without CVE ids include three more criticals: a skipAuth option that disabled dashboard authentication entirely, unauthenticated stdio server registration when that option was on, and an SSE endpoint that accepted an arbitrary username from the URL path. The CVE feed alone shows less than half of what the project has disclosed; the repository's advisory index is the complete record, and v1.0.32 is the release that closes out the newest of it.

How was this verified, and what are the sources?

Published · last verified · confidence 1.00.

  1. CVE-2026-79748 CNA record (GitHub) - "Authenticated non-admin user achieves RCE via POST /api/servers (missing authorization on stdio command/args)", CVSS 3.1 9.9 critical, affected below 0.12.15; published 2026-08-31, one of eight MCPHub records reserved together on 2026-08-25 - accessed
  2. samanhappy/mcphub repository security advisories - 18 published advisories; the eight carrying CVE ids went out 2026-08-17 to 2026-08-23 (the MCPB path traversal on 2026-04-19); ten more have no CVE id, including three criticals (skipAuth disabling dashboard auth, skipAuth stdio registration RCE, SSE endpoint username impersonation) - accessed
  3. MCPHub releases - every fix predates its record: v0.12.13 (2026-04-22), v0.12.15 (2026-05-02), v1.0.29 (2026-08-17), v1.0.30 (2026-08-20), v1.0.31 (2026-08-22), v1.0.32 (2026-08-23) - accessed

← All news