CVE-2026-9958: Google Chrome · Use After Free
Affects Google ChromeSource CVE Database V5
Not known to be exploited · CVSS 8.8 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:L/PR:N/UI:R/S:U/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 fix in Chrome version 148.0.7778.216. Users and administrators should update to this version or later to remediate the vulnerability. Since this is a client-side vulnerability requiring user interaction, applying the update is the primary mitigation. No additional vendor-recommended mitigations or workarounds are indicated in the advisory.
Description
CVE-2026-9958 is a use-after-free vulnerability in the PDFium component of Google Chrome versions prior to 148.0.7778.216. This flaw allows a remote attacker to potentially cause heap corruption by crafting a malicious PDF file. The vulnerability has a high severity rating and a CVSS score of 8.8, indicating significant impact on confidentiality, integrity, and availability. There are no known exploits in the wild at this time. The vendor advisory linked corresponds to a stable channel update addressing this issue.