CVE-2026-9884: 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.3% chance of exploitation in 30 days – higher than 30% 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
Users should refer to the official Google Chrome stable channel update blog post for the latest remediation guidance. Until confirmation of patch availability, users should exercise caution when browsing untrusted websites and avoid interacting with suspicious HTML content.
Description
CVE-2026-9884 is a use-after-free vulnerability in the Browser component of Google Chrome on Mac systems prior to version 148.0.7778.216. This flaw allows a remote attacker to execute arbitrary code by tricking a user into visiting a crafted HTML page. The vulnerability is rated with a high severity CVSS score of 8.8, indicating significant potential impact on confidentiality, integrity, and availability. The issue was publicly disclosed on May 28, 2026. There is no explicit vendor advisory detail confirming patch availability or remediation level in the provided data, though a Google Chrome stable channel update blog post is referenced. No known exploits in the wild have been reported at this time.