CVE-2026-11063
A flaw in Google Chrome’s WebNN component on Windows lets a remote attacker escape the browser sandbox if they already control the renderer process. The bug is triggered by specially crafted HTML and can lead to full system compromise. It is fixed in Chrome 149.0.7827.53 and later.
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 who can run code in Chrome’s renderer process could break out of the browser sandbox and gain full control of the Windows system, allowing them to read, modify, or delete files, install malware, or steal data.
Why this severity
The CVSS score of 9.6 reflects that the vulnerability is exploitable over the network, requires no special privileges, and can lead to complete compromise of confidentiality, integrity, and availability.
What to do about it
- 01Upgrade Google Chrome to version 149.0.7827.53 or later.
- 02Restart the browser.
NVD description indicates fix in Chrome version 149.0.7827.53 or later.
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/499051067permissions required