Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2026-2805 is a critical-severity Access of Uninitialized Pointer (CWE-824) vulnerability in Mozilla Firefox. Its CVSS base score is 9.8 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); 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-2805 is an invalid pointer vulnerability in the DOM Core & HTML component of Mozilla Firefox and Thunderbird. The issue, associated with CWE-824 (Access of Uninitialized Pointer), allows for critical memory corruption and was assigned a CVSS v3.1 base score of 9.8, reflecting its high severity due to network accessibility, low attack complexity, and no requirements for privileges or user interaction.
Remote attackers can exploit this vulnerability over the network without authentication or user interaction to achieve high-impact confidentiality, integrity, and availability violations. Successful exploitation could lead to arbitrary code execution, data exposure, or system compromise within the browser's sandboxed environment.
Mozilla's security advisories (MFSA 2026-13 and MFSA 2026-16) and Bugzilla entry (bug 2014549) detail the fix applied in Firefox 148 and Thunderbird 148. Security practitioners should ensure users update to these versions or later to mitigate the risk, as no workarounds are specified in the provided references.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-8458
Vulnerability Data
Invalid pointer in the DOM: Core & HTML component. This vulnerability was fixed in Firefox 148 and Thunderbird 148.
- 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 can discover uninitialized pointer accesses through static analysis, dynamic testing, or fuzzing before deployment.
Requiring documented development processes and tools enables use of analyzers or coding standards that identify uninitialized pointer defects.
Security engineering principles can mandate memory-safety practices and language choices that structurally avoid uninitialized pointer use.
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 uninitialized pointer bugs via coding standards, analysis, and reviews, but eliminating this single weakness only partially fulfills the broader control.
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 uninitialized pointer usage before release.
Secure development life cycle mandates practices that reduce uninitialized pointer defects.
Application security requirements can specify pointer initialization rules.
Secure architecture principles discourage unsafe pointer handling.
Secure coding standards directly prohibit use of uninitialized pointers.