Skip to main content
VulnerabilityPublished Updated

CVE-2026-10002: Google Chrome · Use After Free

Affects Google ChromeSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.8 High : upgrade to 148.0.7778.216 soon.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 7% 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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 29 Oct 2026.

What to do

Upgrade Google Chrome to 148.0.7778.216.

Affected software

ProductAffectedFixed in
GoogleChromeAffected
  • >=148.0.7778.216 <148.0.7778.216
Fixed in
  • 148.0.7778.216

AI-suggested

Google has released a stable channel update for Chrome version 148.0.7778.216 that fixes this vulnerability. Users and administrators should update to this version or later to remediate the issue. Patch status is confirmed by the vendor advisory linked in the report.

Description

CVE-2026-10002 is a high-severity 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 requires user interaction to exploit and affects confidentiality, integrity, and availability. Google has published a stable channel update addressing this issue.

References

Community reviews

Loading reviews…