Hangwin mcp-chrome-bridge
mcp-chrome-bridge through 1.0.31 CORS Origin Bypass
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.
First public PoC
16 daysafter publication · 15 Oct 2026 · nuclei template
Public PoCs10 on GitHub · 1 Exploit-DB, Metasploit or nuclei
CVSS8.6high · scored by CNA · CWE-346
CISA KEV
Not listednot known exploited
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
hangwin mcp-chrome-bridge
- <= 1.0.31
Mitigation
The record names no fix. Check the vendor advisory below.
Timeline
Days relative to CVE publicationFirst public PoC 16 days after publication; not in CISA KEV. First PoC: nuclei template: mcp-chrome-bridge (hangwin/mcp-chrome) <= 1.0.31 - CORS Origin Bypass (CSWSH) (nuclei template, 15 Oct 2026).
PoC repositories
Found on GitHub.No PoC repositories found yet.
Other public exploits
Exploit-DB, Metasploit and nuclei count as public PoCs. Exploit-tagged references from the CVE record and NVD are links only. None of these are analysed by us.| Source | Title | Published | Found by us |
|---|---|---|---|
| nuclei template | nuclei template: mcp-chrome-bridge (hangwin/mcp-chrome) <= 1.0.31 - CORS Origin Bypass (CSWSH) | 15 Oct 2026 | 14 Nov 2026 |