Skip to content

AAK-MCP-CHROMEBRIDGE-CVE-2026-102878-001: mcp-chrome-bridge, every release (no fix): the native server's HTTP MCP endpoint answers web pages

Severity
HIGH
Category
Supply Chain (supply-chain)
Scanner
agent_audit_kit/scanners/mcp_cve_pins_2026_07.py
Auto-fixable
No.
SARIF name
McpChromeBridgeCorsOriginBypass

What it detects

mcp-chrome-bridge (mcp-chrome-bridge on npm), the native server of hangwin/mcp-chrome, connects a Chrome extension to MCP clients and serves the extension's tools, which navigate, run script in pages, read page content and take screenshots, over HTTP on 127.0.0.1 (/mcp, /sse, /messages). Its CORS check lets web pages call those endpoints (CVE-2026-102878, CVSS 8.1, CWE-346): through 1.0.29 it registers @fastify/cors with origin: true, which accepts every origin, and 1.0.30 and 1.0.31 compare the Origin with startsWith('http://127.0.0.1') and allow credentials, so a page served from a host such as 127.0.0.1.example.com passes. A page the user opens can then call the tools in the user's browser. Checked in every npm tarball from 1.0.0 to 1.0.31 (2025-12-30, the newest). There is no fixed release: hangwin/mcp-chrome#384 is open with no reply, and nothing has been committed upstream since 2026-01-06.

How to fix

There is no fixed version. Remove mcp-chrome-bridge and the extension where they are not needed. Where they are, do not leave the native server running while you browse sites you do not trust, and do not run it in a browser profile signed in to accounts that matter. A fork closes the hole by matching the Origin exactly against the extension's own origin.

To confirm the finding is gone, report only this rule:

agent-audit-kit scan . --rules AAK-MCP-CHROMEBRIDGE-CVE-2026-102878-001

Limitations

Reports an npm reference to mcp-chrome-bridge, with or without a version, since every release is affected and none is fixed: a package.json or lockfile entry at the project root, the package an npx launch in an MCP config names, or a config that runs a global install by that bare name. The upstream README installs it globally and connects a client by URL (http://127.0.0.1:12306/mcp) or by the path of mcp-server-stdio.js inside the global install; neither names the package, so neither is reported, and neither is a config that runs the package's other commands, mcp-chrome-stdio and chrome-mcp-bridge, by name. It reads the name and version, not whether the server is running. A file over 2 MB, or a lockfile over 32 MiB, is not read. A declaration nested more than 64 levels deep in package.json, a TOML manifest or an MCP config (an MCP server more than 62) is still judged, and reported without a line; a lockfile entry keeps its line at any depth.

References


All rules. This page is generated from the rule registry when the documentation is built; to change it, change the rule in agent_audit_kit/rules/builtin.py. To give the rule a hand-written write-up, add docs/rules/AAK-MCP-CHROMEBRIDGE-CVE-2026-102878-001.md: the page then shows that text, with the registry reference appended under it.