Skip to main content
CVE-2025-12380VulnerabilityPublished Updated

CVE-2025-12380: Mozilla Firefox · Vulnerability

Affects Mozilla FirefoxSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical : upgrade to 144.0.2 as a priority.

Data as of 25 Oct 2026, 19:02 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Oct 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 2026-10-25.

What to do

Upgrade Mozilla Firefox to 144.0.2.

Affected software

ProductAffectedFixed in
Mozilla FirefoxAffected
  • >=142 <144.0.2
Fixed in
  • 144.0.2

AI-suggested

Mozilla has released an official fix for this vulnerability in Firefox version 144.0.2. Users and administrators should update affected Firefox installations to version 144.0.2 or later to remediate this issue. No additional mitigation steps are indicated by the vendor advisory.

Description

A use-after-free vulnerability exists in Mozilla Firefox starting from version 142 through before 144.0.2. This flaw involves WebGPU-related IPC calls that allow a compromised child process to trigger memory corruption in the GPU or browser process. The vulnerability could potentially be exploited to escape the child process sandbox. Mozilla fixed this issue in Firefox 144.0.2.

References

Community reviews

Loading reviews…