basicsecurity.net
Proof, not just disclosure.
Threats / Mozilla / CVE-2022-26485
CVE-2022-26485 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

Mozilla Firefox vulnerability

Mozilla Firefox contains a use-after-free vulnerability in XSLT parameter processing that enables arbitrary code execution.

Verdict

Today item — known-exploited.

A use-after-free flaw in Firefox's XSLT parameter handling allows attackers to execute arbitrary code through crafted content. The vulnerability has been observed in active exploitation in the wild.

CISA KEV Yes · 2022-03-073EPSS 0.14261 (verify live)4Exploit Public PoC5
01

Is it exploitable?

— the evidence, ranked above the score
Exploit available
Public proof-of-concept exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
6 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2022-03-07).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.14261 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Mozilla, Firefox. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-416 Use After Free — weakness family: Memory safety.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
WeaknessCWE-416 · Use After FreeMemory safety
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution not established

No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.

03

Why it matters

— the attack path, told twice: adversary, then board
1

Front door — unauthenticated access narrative 1

Attacker
I craft malicious XSLT content with specially formed parameters to trigger a use-after-free condition in Firefox's processing engine.
Business
Users visiting attacker-controlled or compromised websites face arbitrary code execution on their systems without additional user interaction.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I deliver the malicious XSLT payload through web content, email attachments, or compromised legitimate websites to reach target Firefox users.
Business
Attackers gain code execution capability on victim machines, enabling data theft, malware installation, or lateral movement within networks.
04

What to do

— defensible action
  • Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • Public PoC available (VulnCheck)
  • 6 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Public exploit availability
  • Catalogued by mozilla (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by mozillaCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.