CVE-2026-11095
A critical flaw in Google Chrome’s codecs lets a remote attacker escape the browser sandbox if they can compromise the renderer process. The issue stems from insufficient validation of untrusted input in a crafted HTML page. Updating to Chrome 149.0.7827.53 or newer resolves the vulnerability.
An official fix is available, so this entry is kept for 30 days and then removed automatically.
Who is affected
Google Chrome users running versions older than 149.0.7827.53, particularly those who may view untrusted web content.
Real-world impact
An attacker who tricks a user into loading a malicious HTML page could break out of the browser sandbox and gain full system access, potentially compromising the entire machine.
Why this severity
The CVSS score of 9.6 reflects the high impact of a sandbox escape, the lack of authentication required, and the fact that the attacker must first compromise the renderer process.
What to do about it
- 01Update Google Chrome to version 149.0.7827.53 or newer.
- 02Restart the browser after the update.
NVD-referenced vendor advisory
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 24, 2026 · 11d 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…release notes
- issues.chromium.org/issues/500293394permissions required