Payload: Improper access control for MCP API keys
CVE-2026-105806 · GHSA-2q76-m6w6-qgc6 · published 2026-10-06
- Severity
- High
- CVSS score
- 8.6
- Chance of exploitation (EPSS)
- 0.25%
- Fixed in
- 3.88.0
- Exploitation No known exploitation
- Automatable No
- Technical impact Partial
- CISA SSVC
Under certain conditions, an authenticated user could manage MCP API keys outside their intended account allowing an attacker to escalate privileges through account takeover. Applications that do not use @payloadcms/plugin-mcp are not affected.
Upgrade @payloadcms/plugin-mcp to 3.88.0 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.
Users should upgrade to @payloadcms/plugin-mcp version 3.88.0 or later.
Upgrading is recommended. Until then, disable the MCP plugin or restrict MCP API-key management to trusted users.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| @payloadcms/plugin-mcp | npm | >= 3.61.0, < 3.88.0 | 3.88.0 |
- CriticalMarimo: Pre-Auth Remote Code Execution via Terminal WebSocket Authentication BypassmarimoExploited
- CriticalLangflow CORS misconfiguration enables Account Takeover and RCElangflowExploited
- HighLiteLLM: MCP Authentication Bypass via OAuth2 Passthrough FallbacklitellmExploited
- HighLangflow: IDOR Vulnerability in `/api/v1/responses` Endpoint Allows Authenticated Attackers to Access Another User's FlowlangflowExploited
- CriticalTodoist MCP Server: Browser DNS rebinding lets websites write and delete Todoist data through local MCP server@doist/todoist-mcp
- CriticalLangflow: Unauthenticated Flow Execution via Webhook Authentication Bypasslangflow
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.