UTC
High

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
What it is

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.

What to do

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.

Affected
PackageRegistryAffectedFixed in
camofox-mcpnpm< 1.13.21.13.2

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.

Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].