CVE-2025-1012

CVE-2025-1012 is a high-severity vulnerability in Mozilla Firefox with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-416.

Key facts

Description

A race during concurrent delazification could have led to a use-after-free. This vulnerability was fixed in Firefox 135, Firefox ESR 115.20, Firefox ESR 128.7, Thunderbird 128.7, and Thunderbird 135.

Frequently asked questions

What is CVE-2025-1012?
A race during concurrent delazification could have led to a use-after-free. This vulnerability was fixed in Firefox 135, Firefox ESR 115.20, Firefox ESR 128.7, Thunderbird 128.7, and Thunderbird 135.
How severe is CVE-2025-1012?
CVE-2025-1012 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with high attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2025-1012 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (35th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-1012?
CVE-2025-1012 primarily affects Mozilla Firefox. In total, 4 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2025-1012?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2025-1012 have an EU (EUVD) identifier?
Yes. CVE-2025-1012 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-1967.
When was CVE-2025-1012 published?
CVE-2025-1012 was published on 2025-02-04 and last updated on 2026-06-17.

References

Affected products (4)

More vulnerabilities in Mozilla Firefox

All CVEs affecting Mozilla Firefox →

Other CWE-416 (Use After Free) vulnerabilities

Browse all CWE-416 (Use After Free) vulnerabilities →