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

> Attackers can bypass CORS restrictions to invoke browser automation tools, enabling script execution and data theft via malicious web pages.

- **Severity:** High 8.6 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 29 Sep 2026
- **Updated:** 29 Sep 2026
- **Also known as:** GHSA-wfc7-pjhg-rg95

## What is CVE-2026-102878?

CVE-2026-102878 is a high-severity vulnerability in hangwin mcp-chrome-bridge, published on 29 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-346 (Origin Validation Error)

## Which versions are affected by CVE-2026-102878?


## How do I fix CVE-2026-102878?

No fix has been published for CVE-2026-102878 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-102878 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-102878 exists.

Public exploit code:

- mcp-chrome-bridge (hangwin/mcp-chrome) <= 1.0.31 - CORS Origin Bypass (CSWSH) (nuclei): http/cves/2026/CVE-2026-102878.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-102878 and fix it if it is affected.

What it is: CVE-2026-102878 is a high-severity vulnerability in hangwin mcp-chrome-bridge, published on 29 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-102878 exists.

Affected product: hangwin mcp-chrome-bridge. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-102878/ (Markdown: https://insights.sbomify.com/CVE-2026-102878/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-102878
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-102878
- OSV: https://osv.dev/vulnerability/CVE-2026-102878

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-102878/
Summaries are generated and may contain mistakes; the official description above is the record.