Cyber Resilience

CVE-2026-2796

Memory Safety in Mozilla Firefox ≤ 148.0

Memory Safety
Published
24 February 2026
Modified
15 July 2026
Patch / advisory
View advisory
CVSS Score v3.1 9.8
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:H/A:H
EPSS Score 0.0063 47th percentile
Risk Priority 72 floored blend · peak EPSS

Summary

CVE-2026-2796 is a critical-severity Type Confusion (CWE-843) 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 47th 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-8 (Security and Privacy Engineering Principles) — 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-2796 is a JIT miscompilation vulnerability in the JavaScript: WebAssembly component of Mozilla Firefox and Thunderbird. This flaw, classified under CWE-843 (incorrect type conversion or cast), allows for improper handling during just-in-time compilation of WebAssembly code, potentially leading to exploitable memory corruption. It affects versions of Firefox and Thunderbird prior to 148 and carries a CVSS v3.1 base score of 9.8, indicating critical severity due to its high impact on confidentiality, integrity, and availability.

A remote attacker can exploit this vulnerability over the network with low attack complexity, requiring no privileges, user interaction, or scope changes. By crafting malicious WebAssembly content deliverable via a website or other network-accessible vector, the attacker could trigger the miscompilation, enabling arbitrary code execution within the browser's sandboxed JavaScript engine. Successful exploitation would grant high-impact control over the affected process, potentially compromising the victim's system if chained with sandbox escapes.

Mozilla addressed this issue in Firefox 148 and Thunderbird 148, as detailed in security advisories MFSA 2026-13 and MFSA 2026-16, along with the upstream bug report at Bugzilla ID 2013165. Security practitioners should prioritize updating affected browsers to these patched versions and monitor for similar JIT-related issues in WebAssembly implementations.

EU & UK References

Vulnerability Data

JIT miscompilation in the JavaScript: WebAssembly component. This vulnerability was fixed in Firefox 148 and Thunderbird 148.

CWE(s)
CWE-843

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
attack.mitre.org →
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-14325Same product: Mozilla Firefox
CVE-2019-11707Same product: Mozilla Firefox
CVE-2026-74956Same product: Mozilla Firefox
CVE-2026-16355Same product: Mozilla Firefox
CVE-2026-16410Same product: Mozilla Firefox
CVE-2026-16392Same product: Mozilla Firefox
CVE-2026-16363Same product: Mozilla Firefox
CVE-2025-14330Same product: Mozilla Firefox
CVE-2024-7652Same product: Mozilla Firefox
CVE-2026-12299Same product: Mozilla Firefox

Affected Assets

mozilla
firefox
≤ 148.0
mozilla
thunderbird
≤ 148.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.5.2
  • V3.2.3
  • V15.3.5

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation (including fuzzing and type-aware analysis) directly finds type-confusion flaws before deployment.

SA-8 Security and Privacy Engineering Principles partial match

Engineering principles can require use of type-safe languages, static typing, and runtime type checks that structurally avoid allocating one type and accessing another.

SI-16 Memory Protection partial match

Memory-protection controls limit the blast radius when a type-confusion access occurs but do not stop the flaw itself.

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 practices directly prevent type-confusion flaws via safe typing, static analysis, and code review while the control itself addresses many additional 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.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development can detect type-confusion vulnerabilities through fuzzing and static analysis.

A.8.25 Secure development life cycle partial match
prevents

Secure SDLC mandates type-safe design and review that can catch type-confusion flaws.

A.8.26 Application security requirements partial match
prevents

Application security requirements can specify strong typing and interface contracts that reduce type confusion.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles promote type-safe languages and memory-safety mechanisms that mitigate type confusion.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly forbid unsafe type casts and require static-analysis checks for type confusion.

References