CVE-2026-11082
A race condition in Chrome’s GPU code on Android lets a malicious web page escape the browser sandbox if the attacker already controls the renderer process. This could let the attacker gain full system access on the device. The flaw is only present in Chrome versions older than 149.0.7827.53.
No official fix yet. If none appears within 45 days of first tracking, this entry is removed automatically.
Who is affected
Google Chrome for Android versions earlier than 149.0.7827.53. Android users running those versions are at risk.
Real-world impact
If an attacker can run code in the renderer process, they could break out of the browser sandbox and execute arbitrary code on the Android device, potentially stealing data or taking control.
Why this severity
The CVSS score of 9.6 reflects that the vulnerability can be triggered over the network, requires no special privileges, needs user interaction to load a crafted page, and changes the scope of the affected component. The high impact on confidentiality, integrity, and availability drives the score.
What to do about it
No official fix or mitigation is documented in the sources yet. Monitor the vendor advisory and apply the patch as soon as it is released.
No fix documented in sources
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.
How it’s attacked
References & advisories
- chromereleases.googleblog.com/2026/06/stable-channel-upda…vendor advisory
- issues.chromium.org/issues/500079715permissions required