CamoFox MCP: Unauthenticated HTTP MCP browser-control surface
GHSA-7hgr-7h44-33w2 · published 2026-05-19
- Severity
- High
- CVSS score
- 7.0
- Chance of exploitation (EPSS)
- No CVE
- Fixed in
- 1.13.2
An unauthenticated client that can reach the HTTP MCP endpoint can exercise browser-control tools as the MCP server. Depending on the user's active browser profiles and configured backend, that can allow page navigation, tab creation, interaction with authenticated browser contexts, screenshot/content observation, and other browser-automation actions exposed by the MCP tool surface. The impact is strongest when HTTP mode is intentionally exposed for remote MCP clients or through Docker/reverse-proxy deployment and the operator assumes CAMOFOXAPIKEY protects the whole control plane.
Upgrade camofox-mcp to 1.13.2 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.
The public issue indicates this has been fixed in 599f56e and released as v1.13.2 by adding dedicated inbound CAMOFOXHTTPAPI_KEY Bearer auth, public-bind startup validation, auth before /mcp JSON parsing, loopback Host-header protection, and optional allowed-hosts handling. Those are the right mitigation directions.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| camofox-mcp | npm | < 1.13.2 | 1.13.2 |
- 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.