CVE-2025-8028
Mozilla Firefox ≤ 115.26.0
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2025-8028 is a critical-severity Improper Handling of Faults that Lead to Instruction Skips (CWE-1332) vulnerability in Mozilla Firefox. Its CVSS base score is 9.8 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Pre-OS Boot (T1542); ranked at the 39th 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-18 (Tamper Resistance and Detection) and SR-9 (Tamper Resistance and Detection) — 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-8028 is a critical vulnerability in the WebAssembly (WASM) engine of Mozilla Firefox and Thunderbird browsers, specifically affecting arm64 architectures. The issue arises when processing a WASM `br_table` instruction with a large number of entries, causing the label distance from the instruction to exceed limits, resulting in truncation and incorrect computation of the branch target address. This flaw, classified under CWE-1332 (Incorrect Branch Target), impacts versions of Firefox prior to 141, Firefox ESR prior to 115.26, 128.13, and 140.1, as well as Thunderbird prior to 141, 128.13, and 140.1. It carries a CVSS v3.1 base score of 9.8, indicating high severity due to its potential for confidentially, integrity, and availability impacts.
A remote attacker can exploit this vulnerability without privileges or user interaction by tricking a victim into loading a malicious webpage containing specially crafted WASM code. On vulnerable arm64 systems running affected browser versions, the flawed branch computation enables arbitrary code execution within the browser's sandbox, potentially leading to full compromise of the user's system through escalation beyond the sandbox.
Mozilla's security advisories (MFSA 2025-56 through 59) and the associated Bugzilla entry confirm the vulnerability has been patched in the listed Firefox and Thunderbird versions. Security practitioners should prioritize updating affected browsers on arm64 platforms, such as Apple Silicon Macs or ARM-based Linux systems, to mitigate exploitation risks.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-22371
Vulnerability Data
On arm64, a WASM `br_table` instruction with a lot of entries could lead to the label being too far from the instruction causing truncation and incorrect computation of the branch address. This vulnerability was fixed in Firefox 141, Firefox ESR…
more
115.26, Firefox ESR 128.13, Firefox ESR 140.1, Thunderbird 141, Thunderbird 128.13, and Thunderbird 140.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
Tamper resistance and detection requirements prevent the absence of fault-handling mechanisms for instruction-skipping attacks.
Tamper protection program directly requires circuitry/sensors to detect and respond to physical fault injection that produces instruction skips.
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.
Replacing hardware that lacks required security capabilities (e.g., fault sensors) directly mitigates the described weakness.
Protecting assets from environmental threats can reduce fault-injection opportunities that cause instruction skips.
Resilience mechanisms can include hardware-level fault detection and recovery that directly address instruction skips.
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.
Secure system architecture and engineering principles can require hardware-level fault detection and instruction-integrity mechanisms.
Secure coding guidelines may mandate defensive coding against skipped instructions, but do not address underlying hardware circuitry.
Security testing in development can discover instruction-skip faults, yet testing alone does not guarantee hardware-level mitigation.