Security Resilience

CVE-2025-0241

Mozilla Firefox ≤ 128.6.0

Published
07 January 2025
Modified
05 October 2026
Patch / advisory
CVSS Score v3.1 7.7
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:L
EPSS Score 0.0073 54th percentile
Risk Priority 58 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2025-0241 is a high-severity Missing Release of Memory after Effective Lifetime (CWE-401) vulnerability in Mozilla Firefox. Its CVSS base score is 7.7 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Endpoint Denial of Service (T1499); ranked in the top 46% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2025-0241 is a memory corruption vulnerability triggered during the segmentation of specially crafted text in Mozilla products. The flaw causes memory corruption that can lead to a potentially exploitable crash. It affects Firefox versions prior to 134, Firefox ESR versions prior to 128.6, Thunderbird versions prior to 134, and Thunderbird ESR versions prior to 128.6.

The vulnerability carries a CVSS v3.1 base score of 7.7 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:L). Remote attackers with no required privileges or user interaction can exploit it over the network, though it demands high attack complexity. Successful exploitation enables high-impact confidentiality and integrity violations, such as unauthorized data access or modification, alongside low-impact availability disruption through a crash.

Mozilla advisories MFSA 2025-01, MFSA 2025-02, MFSA 2025-04, and MFSA 2025-05, along with Bugzilla entry 1933023, confirm the issue was fixed in Firefox 134, Firefox ESR 128.6, Thunderbird 134, and Thunderbird 128.6. Users should update to these patched versions for mitigation.

EU & UK References

Vulnerability Data

When segmenting specially crafted text, segmentation would corrupt memory leading to a potentially exploitable crash. This vulnerability was fixed in Firefox 134, Firefox ESR 128.6, Thunderbird 134, and Thunderbird 128.6.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1499 Endpoint Denial of Service Impact
Adversaries may perform Endpoint Denial of Service (DoS) attacks to degrade or block the availability of services to users.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-3860Same product: Mozilla Firefox
CVE-2023-5170Same product: Mozilla Firefox
CVE-2026-12298Same product: Mozilla Firefox
CVE-2026-16353Same product: Mozilla Firefox
CVE-2026-8948Same product: Mozilla Firefox
CVE-2026-8092Same product: Mozilla Firefox
CVE-2026-6786Same product: Mozilla Firefox
CVE-2026-12310Same product: Mozilla Firefox
CVE-2026-12314Same product: Mozilla Firefox
CVE-2026-6784Same product: Mozilla Firefox

Affected Assets

mozilla
firefox
≤ 128.6.0 · ≤ 134.0
mozilla
thunderbird
≤ 128.6.0 · 129.0 — 134.0

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation (static analysis, fuzzing, or runtime leak detection) directly finds missing deallocation.

Requiring documented development standards and tools can mandate memory-management disciplines that avoid leaks at introduction.

Engineering principles applied during development can require explicit resource-release patterns that stop memory leaks from being coded.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
blocks

Secure SDLC practices directly enforce proper memory allocation/deallocation via coding standards, reviews, and tooling.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing in development can detect unreleased memory, providing partial coverage of the weakness.

prevents

Secure coding standards directly require proper allocation/deallocation, covering most of this weakness.

finds

Capacity management may detect memory exhaustion symptoms but does not prevent the coding flaw.

References