CVE-2026-74947
Mozilla Firefox ≤ 153.1.0
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HSummary
CVE-2026-74947 is a high-severity Release of Invalid Pointer or Reference (CWE-763) vulnerability in Mozilla Firefox. Its CVSS base score is 8.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 16th 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.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-60677
Vulnerability Data
Privilege escalation due to invalid pointer in the Graphics component. This vulnerability was fixed in Firefox 154, Firefox ESR 153.1, Thunderbird 154, and Thunderbird 153.1.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation directly exercises deallocation paths and can find incorrect release calls or mismatched alloc/free pairs.
Documented development standards and tools can mandate safe memory-management idioms and static checks that avoid invalid releases.
An SDLC that incorporates security can embed memory-safety requirements, reducing the chance such coding errors are introduced.
Engineering principles require correct resource management and memory-release patterns that stop invalid pointer releases 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.
Secure SDLC practices directly prevent invalid pointer release errors during development.
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.
Security testing can detect invalid pointer releases before release.
Secure SDLC practices can mandate proper memory-management APIs and reviews that catch incorrect deallocation.
Application security requirements can specify correct use of release functions and pointer validation.
Secure architecture principles include safe memory handling and resource-lifetime rules.
Secure coding standards directly prohibit mismatched or incorrect pointer-release calls.