Black Friday60% off BLACKFRIDAY2026
PlatformPlansPartners
Resources
ToolsBlogDocs
Sign Up →
high·Misconfiguration·Updated Nov 9, 2026

CVE-2026-102878 Scanner

CVE-2026-102878 Scanner - Cross-Site WebSocket Hijacking (CSWSH) vulnerability in mcp-chrome-bridge

Est. Time~10 seconds
Scan TypeSingle Scan
Targetsdomain, subdomain, ipv4
CostFree
5
Times Used
continuous scan runs
4.2k
Continuously Checked
assets under CS
0
Vulnerabilities Found
confirmed findings
References
8.6
CVSShigh
Exploitable remotely over the internet · no authentication required.
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.

Attack Vector
Network
Privileges Req.
None
User Interaction
P
Affected
mcp-chrome-bridgeby hangwin
0
Updated Nov 6, 2026View on NVD →
Detail

The mcp-chrome-bridge is a critical component used widely across various platforms to enable interactive web functionalities. Developed by hangwin, it supports various operations such as executing scripts, navigating through web pages, and managing cookies in Chrome instances for automation purposes. Many IT and web development companies integrate this bridge into their applications to facilitate efficient browser automation tasks. Its primary function is to ease automation processes by acting as a bridge between client-side applications and the Chrome browser. The software is popular among developers due to its seamless integration features and compatibility with a wide range of web automation tools. However, as vital as mcp-chrome-bridge is, ensuring its security is paramount to protect against potential cyber threats.

The vulnerability focuses on Cross-Site WebSocket Hijacking (CSWSH), which poses a significant risk to web applications by enabling unauthorized access and manipulation through WebSocket connections. Attackers can exploit this flaw by initiating unauthorized WebSocket connections from malicious origins, thereby bypassing CORS policies. This can lead to unauthorized interactions with the local server. The vulnerability can allow arbitrary codes to be executed, which can compromise data integrity and confidentiality. By exploiting this vulnerability, attackers can gain access to sensitive information and manipulate browser automation tools that rely on WebSockets for real-time communications. Such vulnerabilities highlight the importance of stringent origin validation and strengthening security measures around WebSocket connections.

Technical exposure in mcp-chrome-bridge arises due to the improper handling of CORS policies. The software uses origin.startsWith for CORS checks, which is susceptible to bypassing through manipulative subdomain names like http://127.0.0.1.evil.com. This misconfiguration allows potentially harmful external websites to perform credentialed cross-origin requests. Attackers can exploit this by serving malicious content over a crafted domain name designed to appear permissible. By doing so, they can undertake unauthorized actions such as executing scripts, stealing session cookies, or even extracting screenshots. This vulnerability primarily occurs when developers fail to sanitize origin entries properly, which could compromise server integrity and lead directly to data leaks.

When the CSWSH vulnerability is exploited, attackers can initiate unauthorized access to sensitive data via the browser's automation tools. Consequences include manipulation of browser sessions, unauthorized script execution, and data theft through cookie/session access. This exploitation could cause significant harm by mishandling sensitive operations and viewing confidential information, leading to broader compromises like altered website behavior or unauthorized usage of browser-automation functionalities. Organizations risk losing control over their automated tools, which could lead to unauthorized transactions or operations, and potentially impact business operations due to web automation disruptions.

REFERENCES

Solution Advice
  • Update mcp-chrome-bridge to a version beyond 1.0.31 to mitigate vulnerabilities.
  • Implement stringent CORS policy validation to ensure no unauthorized origins are permitted.
  • Regularly review and test security configurations for WebSocket connections to detect vulnerabilities early.
  • Utilize security tools to automate the scanning for CSWSH and related vulnerabilities.
  • Educate developers on best security practices regarding origin validation and secure coding techniques.

Get AI-powered remediation steps tailored to your asset.

Try AI Solutions →

Check your infrastructure.
Right now.

12,000+ scanners. Free to start. No credit card required.