CVE-2026-12299
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedJIT miscompilation in the DOM: Core & HTML component. This vulnerability was fixed in Firefox 152, Firefox ESR 140.12, Firefox ESR 115.37, Thunderbird 152, and Thunderbird 140.12.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceJIT miscompilation vulnerability in the Firefox/Thunderbird JavaScript engine's DOM Core & HTML component. The Just-In-Time compiler generates incorrect machine code when processing DOM operations, which could lead to memory corruption and potentially allow arbitrary code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 115.37.0< 152.0>= 140.0, < 140.12.0< 152.0.0>= 140.0, < 140.12.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Firefox versionRun 'firefox --version' from command line, or in Firefox navigate to Help > About Firefox to see the exact version numberAffected if Version is less than 115.37.0, or 115.x.x but less than 152.0, or 140.0.x but less than 140.12.0
-
Identify installed Thunderbird versionRun 'thunderbird --version' from command line, or in Thunderbird navigate to Help > About Thunderbird to see the exact version numberAffected if Version is less than 152.0.0, or 140.0.x but less than 140.12.0
-
Verify JIT compilation is enabledIn Firefox address bar, go to 'about:config' and search for 'javascript.options.jit' - check if the value is set to true (enabled). Alternatively, check 'javascript.options.jit.content' preference.Affected if JIT is enabled (value is true) - the vulnerability exists in the JIT compiler, so disabling JIT would mitigate the issue even on a vulnerable version
A user is affected if they are running a vulnerable Firefox or Thunderbird version (as listed above) with JIT compilation enabled.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped115.37.0140.12.0152.0
Update affected installations to Firefox 152, Firefox ESR 115.37/140.12, or Thunderbird 140.12/152 or later versions to receive the JIT compiler fix.
Firefox ESR 115.37, Firefox 152, Firefox ESR 140.12.0, Thunderbird 152, or Thunderbird 140.12.0 (depending on current branch)
- Check current Firefox or Thunderbird version via Help > About (or running --version from command line)
- If running Firefox ESR 115.x: upgrade to Firefox ESR 115.37
- If running Firefox 140.x (or ESR 140.x): upgrade to Firefox ESR 140.12.0
- If running Firefox 141-151: upgrade to Firefox 152
- If running Thunderbird 140.x (or ESR 140.x): upgrade to Thunderbird 140.12.0
- If running Thunderbird before 152: upgrade to Thunderbird 152
- Restart the application after upgrade
- Verify version shows the upgraded release in Help > About
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-12299 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sources- www.mozilla.org
- www.mozilla.org
- www.mozilla.org
- www.mozilla.org
- www.mozilla.org
- bugzilla.mozilla.org
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- bugzilla.redhat.com
- security.access.redhat.com
- nvd.nist.gov
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-12299 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data