@agenticmail/mcp Missing Authentication for Critical Function
CVE-2026-50287 · GHSA-63gr-g7jc-v8rg · published 2026-06-01 · updated 2026-06-12
- Severity
- High
- CVSS score
- 8.7
- Chance of exploitation (EPSS)
- 0.36%
- Fixed in
- 0.9.27
- Exploitation Public proof of concept
- Automatable Yes
- Technical impact Partial
- CISA SSVC
An unauthenticated network client can invoke master-key-only MCP tools through the server, including administrative and gateway actions. Confirmed with a read-only tool: setupguide The same path reaches higher-impact tools such as: setupemailrelay setupemaildomain deleteagent cleanupagents sendtest_email
Upgrade @agenticmail/mcp to 0.9.27 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.
Require authentication for HTTP MCP mode. Bind the MCP HTTP server to 127.0.0.1 by default. Reject /mcp requests that lack a valid bearer token or shared secret. Disable master-key tools when the transport is unauthenticated.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| @agenticmail/mcp | npm | < 0.9.27 | 0.9.27 |
- 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.