CVE-2026-10702: Firefox IonMonkey JIT miscompilation leading to use-after-free
- Vendor
- Mozilla
CVE-2026-10702 is a JIT miscompilation vulnerability in SpiderMonkey's IonMonkey compiler affecting Firefox 147 through 151.0.2 and Tor Browser builds incorporating vulnerable Firefox code. With skipRegistration enabled, MObjectToIterator incorrectly models an operation as a memory read even though lazy property resolution can reallocate an object's dynamic property buffer and free the previous allocation. Global Value Numbering can consequently reuse a stale slots-buffer pointer, producing a use-after-free. Crafted JavaScript can exploit this condition to obtain arbitrary memory read/write and execute code in the browser's renderer process. Firefox 151.0.3 fixes the vulnerability.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation enables arbitrary memory read/write and arbitrary code execution in the Firefox or Tor Browser renderer/content process. Detailed technical accounts describe this execution as sandbox-confined, although other accounts attribute sandbox escape to the same CVE; standalone sandbox escape is therefore disputed. The demonstrated IonStack chain combined this browser vulnerability with the separate Linux kernel vulnerability GhostLock, CVE-2026-43499, to obtain root access on a supported ARM64 Android 17 build. Root-level compromise should not be attributed to CVE-2026-10702 alone.
Mitigation
If you can’t patch tonight, do this now.
Disabling the Ion, Baseline, and Warp JavaScript JIT options is identified as a temporary mitigation. Browser renderer sandboxing limits the consequences of renderer code execution but does not prevent exploitation of the JIT flaw or protect against a separately exploitable sandbox or kernel vulnerability. Updating to a fixed browser release is the preferred remediation.
Remediation
Patch, then assume compromise.
Upgrade Firefox to version 151.0.3 or later. Mozilla corrected the faulty alias modeling by removing MObjectToIterator's custom getAliasSet() override, causing conservative alias handling that accounts for possible object-state changes. For Tor Browser, install a release incorporating the upstream fix; Tor Browser 15.0.19 is identified as a fixed release. Firefox ESR 140.12 is identified as lacking the faulty code path. Patching Firefox blocks the documented IonStack browser entry point but does not remediate CVE-2026-43499.
Exploits
9 exploits validated by Mallory's analysis.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2026-10702 exploited in the wild?
- Yes. As of Oct 14, 2026, Mallory has reports of exploitation in the wild.
- Is there a public exploit for CVE-2026-10702?
- Yes. Mallory tracks 9 public exploits or proofs of concept for CVE-2026-10702, the earliest disclosed Jul 9, 2026.
- Is there a patch for CVE-2026-10702?
- Upgrade Firefox to version 151.0.3 or later. Mozilla corrected the faulty alias modeling by removing MObjectToIterator's custom getAliasSet() override, causing conservative alias handling that accounts for possible object-state changes.
- What products are affected by CVE-2026-10702?
- Mozilla Firefox.
- How severe is CVE-2026-10702?
- CVE-2026-10702 has a CVSS v3.1 score of 7.5 (High) and an EPSS score of 0.86% (59th percentile) as of Oct 14, 2026.
Recent activity
50 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.