Improper access control for MCP API keys in @payloadcms/plugin-mcp
- Product
- @payloadcms/plugin-mcp
- CVE
- CVE-2026-105806
- Affected
- npm/@payloadcms/plugin-mcp 3.61.0 to before 3.88.0
- Fixed in
- 3.88.0
Last verified against sources: October 26, 2026
Am I affected?
@payloadcms/plugin-mcp: affected npm/@payloadcms/plugin-mcp 3.61.0 to before 3.88.0. Fixed in 3.88.0.
- Check your version: run
npm ls @payloadcms/plugin-mcp. Versions >= 3.61.0, < 3.88.0 of @payloadcms/plugin-mcp are affected. [1]
What to do now
- Upgrade to the fixed version: run
npm install @payloadcms/plugin-mcp@3.88.0(first patched version 3.88.0). [1] - Upgrade to @payloadcms/plugin-mcp version 3.88.0 or later. [1]
- Until you upgrade, disable the MCP plugin. [1]
- Until you upgrade, restrict MCP API-key management to trusted users. [1]
General practice, not from the source: if the affected software could read tokens or credentials, rotate them after upgrading; pin versions and review changes before updating tools your agents run.
What happened
Impact
- An attacker could gain higher privileges by taking over an account. [1]
What was done
- The maintainers released @payloadcms/plugin-mcp version 3.88.0, which patches the issue. [1]
Sources
- GHSA-2q76-m6w6-qgc6 — GitHub Advisory Database
Every statement above was checked against these sources before publishing. Spotted an error? Tell us and we will correct it with a dated note.
Share advisory brief with your team
Copy a plain-text summary for Slack, GitHub issues, or team security channels.
[CVE-2026-105806] Improper access control for MCP API keys in @payloadcms/plugin-mcp
Product: @payloadcms/plugin-mcp | Affected: npm/@payloadcms/plugin-mcp 3.61.0 to before 3.88.0 | Fixed in: 3.88.0
Summary: Under certain conditions, a logged-in user could manage MCP API keys outside the account they were meant to use.
Source & remediation on AgentArmorHQ: https://agentarmorhq.com/incidents/2026/10/cve-2026-105806-payloadcms-plugin-mcpCorrections
Report an error or request a correction. We review requests within 5 business days and add a dated correction note.
Discussions for CVE-2026-105806
Ask questions or share configuration tips. Governed by our Community Rules & Terms.
No posts match this filter yet.
Be the first to ask a question or share a working tip.