CVE-2026-9904: 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 stable channel update for Google Chrome has been released to address this vulnerability. Users and administrators should update Chrome to version 148.0.7778.216 or later to mitigate this issue. Since this is not a cloud service, remediation depends on applying the update on client systems. Patch status is confirmed by the vendor advisory at https://chromereleases.googleblog.com/2026/05/stable-channel-update-for-desktop_0877304591.html.
Description
CVE-2026-9904 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 to potentially escape the browser's sandbox by convincing a user to visit a crafted HTML page. The vulnerability has a high severity rating with a CVSS score of 8.3. There are no known exploits in the wild at this time. Google has published a stable channel update addressing this issue.