CVE-2026-9899: Google Chrome · Use After Free
Affects Google ChromeSource CVE Database V5
Not known to be exploited · CVSS 8.3 High : upgrade to 148.0.7778.216 soon.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 148.0.7778.216
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 28 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade Google Chrome to 148.0.7778.216.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| GoogleChrome | Affected
| Fixed in
|
AI-suggested
A fixed version of Google Chrome (148.0.7778.216 or later) has been released by Google to address this vulnerability. Users and administrators should update to this version or a later stable release to remediate the issue. Since this is a client-side application, patching the browser is the primary mitigation. No additional vendor-recommended mitigations or workarounds are indicated in the advisory.
Description
CVE-2026-9899 is a use-after-free vulnerability in the ANGLE component of Google Chrome prior to version 148.0.7778.216. This flaw could allow a remote attacker who has already compromised the renderer process to potentially escape the browser's sandbox by using a specially crafted HTML page. The vulnerability is rated with high severity and has a CVSS score of 8.3. No known exploits in the wild have been reported at this time. The vendor advisory linked corresponds to the Chrome stable channel update addressing this issue.