CVE-2026-11070
A flaw in Google Chrome’s Chromoting feature on Windows allows a remote attacker who has already compromised the network process to potentially escape the browser sandbox by sending specially crafted network traffic.
An official fix is available, so this entry is kept for 30 days and then removed automatically.
Who is affected
Google Chrome on Windows versions earlier than 149.0.7827.53.
Real-world impact
An attacker could break out of the browser sandbox and execute code with the same privileges as the user, potentially taking full control of the affected computer.
Why this severity
The CVSS score of 9.6 reflects the high impact of a sandbox escape (complete compromise of confidentiality, integrity, and availability) combined with the low effort required and the lack of user interaction beyond normal browsing.
What to do about it
- 01Upgrade Google Chrome to version 149.0.7827.53 or later.
- 02Restart the browser to apply the update.
NVD description
Timeline
- Jun 4, 2026 · Jun 4, 2026PublishedDisclosed and added to the National Vulnerability Database.
- Jul 23, 2026 · 12d agoAdvisory updatedThe NVD record was last revised.
- Jul 23, 2026 · 12d agoOfficial fix availableA vendor patch or mitigation now exists — see the remediation steps above.
How it’s attacked
References & advisories
- chromereleases.googleblog.com/2026/06/stable-channel-upda…vendor advisory
- issues.chromium.org/issues/499225384permissions required