CVE-2026-11119
A flaw in Google Chrome on Android lets a remote attacker escape the browser sandbox if they control the renderer process. This could allow the attacker to run code on the device. The vulnerability is considered critical.
An official fix is available, so this entry is kept for 30 days and then removed automatically.
Who is affected
Google Chrome on Android versions before 149.0.7827.53. Users with older Chrome installations on Android devices are at risk.
Real-world impact
An attacker could execute arbitrary code on the device, potentially taking full control of the phone.
Why this severity
The CVSS score of 9.6 reflects that the flaw can be triggered over the network, requires no special privileges, and can compromise confidentiality, integrity, and availability.
What to do about it
- 01Upgrade Google Chrome on Android to version 149.0.7827.53 or later.
- 02Restart the browser.
NVD description indicates fix in version 149.0.7827.53
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…vendor advisory
- issues.chromium.org/issues/501461853permissions required