Cyber Resilience

CVE-2026-4716

Mozilla Firefox ≤ 140.9.0

Published
24 March 2026
Modified
13 April 2026
Patch / advisory
CVSS Score v3.1 9.1
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
EPSS Score 0.0041 34th percentile
Risk Priority 67 floored blend · peak EPSS

Summary

CVE-2026-4716 is a critical-severity Use of Uninitialized Resource (CWE-908) vulnerability in Mozilla Firefox. Its CVSS base score is 9.1 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique OS Credential Dumping (T1003); ranked at the 34th percentile by exploit likelihood (below the median); 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-2026-4716 is a high-severity vulnerability involving incorrect boundary conditions and uninitialized memory in the JavaScript Engine component. It affects Mozilla Firefox versions prior to 149, Firefox ESR prior to 140.9, Thunderbird prior to 149, and Thunderbird prior to 140.9. The issue, classified under CWE-908 (Use of Uninitialized Resource), received a CVSS v3.1 base score of 9.1, reflecting its critical nature due to network accessibility, low attack complexity, and no requirements for privileges or user interaction.

A remote attacker can exploit this vulnerability over the network without authentication or user interaction. Successful exploitation enables high-impact confidentiality violations, such as disclosure of sensitive memory contents, and high-impact availability disruptions, potentially leading to denial-of-service conditions like application crashes, all within the unchanged security scope.

Mozilla addressed the vulnerability in the specified fixed releases: Firefox 149, Firefox ESR 140.9, Thunderbird 149, and Thunderbird 140.9. Security advisories, including MFSA2026-20, MFSA2026-22, MFSA2026-23, and MFSA2026-24, along with Bugzilla entry 2018592, detail the patches and recommend immediate updates to mitigate the risk.

EU & UK References

Vulnerability Data

Incorrect boundary conditions, uninitialized memory in the JavaScript Engine component. This vulnerability was fixed in Firefox 149, Firefox ESR 140.9, Thunderbird 149, and Thunderbird 140.9.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1003 OS Credential Dumping Credential Access
Adversaries may attempt to dump credentials to obtain account login and credential material, normally in the form of a hash or a clear text password.
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
T1552 Unsecured Credentials Credential Access
Adversaries may search compromised systems to find and obtain insecurely stored credentials.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-4715Same product: Mozilla Firefox
CVE-2026-2794Same product: Mozilla Firefox
CVE-2024-3862Same product: Mozilla Firefox
CVE-2026-16386Same product: Mozilla Firefox
CVE-2025-1942Same product: Mozilla Firefox
CVE-2026-16384Same product: Mozilla Firefox
CVE-2026-16385Same product: Mozilla Firefox
CVE-2023-32213Same product: Mozilla Firefox
CVE-2024-7526Same product: Mozilla Firefox
CVE-2026-2806Same product: Mozilla Firefox

Affected Assets

mozilla
firefox
≤ 140.9.0 · ≤ 149.0

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation (including static analysis) can find uses of uninitialized resources after they are coded.

Requiring documented development standards and tools can mandate initialization checks and safe patterns that stop the weakness from being introduced.

Engineering principles can require explicit resource initialization before use, structurally avoiding uninitialized access.

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
prevents

Secure SDLC activities such as static analysis and code review directly prevent use of uninitialized resources while also addressing many other weaknesses.

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 and acceptance can detect uninitialized resource usage through dynamic analysis and fuzzing.

prevents

Secure development life cycle mandates initialization checks and static analysis that can catch uninitialized resource use.

prevents

Application security requirements can specify mandatory initialization of variables and resources before use.

prevents

Secure system architecture and engineering principles include defensive coding practices that prevent use of uninitialized memory or objects.

prevents

Secure coding standards directly require explicit initialization of all variables and resources, substantially mitigating CWE-908.

References