Skip to main content
VulnerabilityPublished

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

Affects Google ChromeSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.6 Critical : upgrade to 154.0.8037.57 as a priority.

Data as of 13 Nov 2026, 23:54 UTC

CVSS 3.1 base score
9.6Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 154.0.8037.57
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Sep 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 14 Nov 2026.

What to do

Upgrade Google Chrome to 154.0.8037.57.

Affected software

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

AI-suggested

An official fix is available. Users should update Google Chrome to version 154.0.8037.57 or later to remediate this vulnerability. No additional mitigation steps are required beyond applying the update.

Description

CVE-2026-95310 is a critical use-after-free vulnerability in the AdFilter component of Google Chrome prior to version 154.0.8037.57. This flaw allows a remote attacker to execute arbitrary code outside the browser sandbox by delivering a specially crafted HTML page. The vulnerability has a high CVSS score of 9.6, indicating severe impact on confidentiality, integrity, and availability. Google has released an update to address this issue.

References

Community reviews

Loading reviews…