Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.0amended

CamoFox MCP: Unauthenticated HTTP MCP browser-control surface

GHSA-7hgr-7h44-33w2

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (camofox-mcp 1.13.2), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
7.0 · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:H/SI:H/SA:L · score source
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

Unauthenticated HTTP MCP browser-control surface in camofox-mcp Summary camofox-mcp exposed a Streamable HTTP MCP endpoint at /mcp with rate limiting but no inbound MCP-layer authentication. When HTTP mode was enabled, any client that could reach /mcp could list and invoke browser-control tools. If CAMOFOXAPIKEY was configured, the server then forwarded that server-side key to the underlying camofox-browser backend. That means an unauthenticated MCP caller could exercise the server's browser authority without knowing the backend browser API key. Reviewed vulnerable commit: 10e3ac08cb50d830eb4ee00a789229f02f28a1a4 Fixed commit observed on main: 599f56ee40f8062aeca541c251ed1d39fb437f50 Fixed release observed: v1.13.2 Suggested severity: High, with the caveat that default loopback-only deployments reduce practical exposure. Root cause In the reviewed commit, src/http.ts creates the Express MCP app and applies only a rate limiter to /mcp: The POST /mcp handler then creates a server and…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-7hgr-7h44-33w2

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-7hgr-7h44-33w2

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-7hgr-7h44-33w2

Advisory: CamoFox MCP: Unauthenticated HTTP MCP browser-control surface
IDs: GHSA-7hgr-7h44-33w2
Record: https://patchnext.com/advisories/ghsa-7hgr-7h44-33w2 (revision 3, source checked 26 Oct 2026, 12:52 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: camofox-mcp 1.13.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm camofox-mcp: affected < 1.13.2; fixed in 1.13.2

## Suggested inspection (read-only)
- `npm ls camofox-mcp --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on camofox-mcp.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-7hgr-7h44-33w2 (OSV record GHSA-7hgr-7h44-33w2 lists affected ranges: npm camofox-mcp >=0 <1.13.2 (fixed))
- Verified: https://github.com/advisories/GHSA-7hgr-7h44-33w2 (GitHub-reviewed advisory GHSA-7hgr-7h44-33w2 lists affected ranges: npm camofox-mcp >=0 <1.13.2)

Commands are suggestions: review each one before running it.

Loading voting…