CVE-2026-10990
A memory error in Google Chrome’s Glic component could let a malicious web page escape the browser sandbox if the renderer process is already compromised. The flaw is a use‑after‑free bug that can lead to arbitrary code execution.
An official fix is available, so this entry is kept for 30 days and then removed automatically.
Who is affected
Google Chrome browsers older than version 149.0.7827.53 on all platforms. Typical users are anyone running an outdated Chrome installation.
Real-world impact
An attacker could run code outside the browser sandbox, potentially taking control of the host system if they can first trick the user into loading a crafted page and have already compromised the renderer process.
Why this severity
The CVSS score of 9.6 reflects that the vulnerability is exploitable over the network, requires no special privileges, and can compromise confidentiality, integrity, and availability. The high impact and low effort to exploit make it critical.
What to do about it
- 011. Update Google Chrome to version 149.0.7827.53 or later.
- 022. Restart 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 22, 2026 · 13d 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…release notes
- issues.chromium.org/issues/506311914permissions required