CVE-2026-9993: 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.1% chance of exploitation in 30 days – higher than 5% 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
Google has released an official stable channel update to fix this vulnerability in Chrome version 148.0.7778.216. Users and administrators should apply this update promptly to mitigate the risk. Since this is a client-side application vulnerability, no additional vendor-managed remediation applies. Patch status is confirmed by the vendor advisory.
Description
CVE-2026-9993 is a use-after-free vulnerability in the Views component of Google Chrome prior to version 148.0.7778.216. This flaw allows a remote attacker who has compromised the renderer process to potentially escape the sandbox by using a specially crafted PDF file. The vulnerability is rated high severity with a CVSS score of 8.3. There are no known exploits in the wild at the time of publication. The vendor advisory linked indicates a stable channel update addressing this issue.