Skip to main content
VulnerabilityPublished Updated

CVE-2025-12438: Google Chrome · Use After Free

Affects Google ChromeSource CVE Database V5

0

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

Data as of 26 Oct 2026, 09:15 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 17% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 142.0.7444.59
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 10 Nov 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 26 Oct 2026.

What to do

Upgrade Google Chrome to 142.0.7444.59.

Affected software

ProductAffectedFixed in
Google ChromeAffected
  • =142.0.7444.59
  • <142.0.7444.59
Fixed in
  • 142.0.7444.59

AI-suggested

To mitigate CVE-2025-12438, organizations should immediately update Google Chrome on Linux and ChromeOS devices to version 142.0.7444.59 or later, where the vulnerability is patched. Beyond patching, organizations should implement browser security best practices such as disabling or restricting JavaScript execution on untrusted sites, employing content security policies (CSP), and using browser isolation technologies to limit the impact of potential exploitation. User education on phishing and safe browsing habits can reduce the likelihood of user interaction with malicious content. Network-level protections, including web filtering and intrusion prevention systems, can help block access to known malicious URLs. Monitoring browser crash logs and unusual behavior may provide early detection of exploitation attempts. For high-security environments, consider restricting the use of Chrome on Linux/ChromeOS or deploying alternative browsers with different codebases until patches are applied.

Description

Use after free in Ozone in Google Chrome on Linux and ChromeOS prior to 142.0.7444.59 allowed a remote attacker to potentially exploit object corruption via a crafted HTML page. (Chromium security severity: Medium)

References

Community reviews

Loading reviews…