← console
voxell vciy

CVE-2026-12323: Spoofing issue in the DOM: Core & HTML component

ROUTINE

Telemetry drift only. No threshold crossed and no authority ruling changed.

CVE record, CISA KEV and EPSS as of 2026-10-18.

CVEs like this one computed, by meaning

What to do now held facts and links

  1. Upgrade to the fixed version for your release line, or later: firefox 152.0.0; thunderbird 152.0.0 upper bounds of the CVE record's affected ranges
  2. Record your decision, dated and frozen with today's evidence: patch by a date · mitigated by a compensating control · deferred · accepted the risk · not affected
  3. Check your version against the ranges this record publishes.

What it is stated by the CNA

Spoofing issue in the DOM: Core & HTML component. This vulnerability was fixed in Firefox 152 and Thunderbird 152.

weakness
Not named by the CNA. NVD maps it to CWE-1021.
affected
Mozilla Firefox; Mozilla Thunderbird
published ranges
mozilla firefox < 152.0.0; mozilla thunderbird < 152.0.0
first unaffected version, by branch
firefox 152.0.0; thunderbird 152.0.0
assigned by
mozilla
published
2026-06-16

check us bugzilla.mozilla.org mozilla.org mozilla.org

Exploit code held, dated

exploit code
None held in the PoC-in-GitHub feed. A public repository changes this brief.

Outside the record researched, cited

This section reads the record's references and adds cited findings from outside it. It needs an account. Everything above is held facts and is complete without it.

Sign in to add the researched section

What would change this brief held, dated

CISA KEV
Not listed in the catalogue we hold. A listing changes this brief.
exploit probability
0.00 on 2026-06-17 (FIRST's EPSS, a probability and not evidence of exploitation). Next band line: 10% (0.10). Crossing a line changes this brief.
fix
Held: firefox 152.0.0; thunderbird 152.0.0. A newer fix from the CNA or OSV changes this brief.

Watch this CVE What counts as a move

How to check this

Every value above is held with two dates: when it was true upstream (as_of) and when we recorded it (tx_from). Re-derive the exploit probability as it stood on any date:

SELECT value, source, source_version, as_of, tx_from
FROM volatile_valid_as_of('CVE-2026-12323', '2026-10-30T23:59:59.999999Z', now());