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

Google Chromium Animation vulnerability

Use-after-free vulnerability in Chromium Animation allows remote attackers to exploit heap corruption through crafted HTML, affecting Chrome, Edge, and other Chromium-based browsers.

Verdict

Today item — known-exploited.

A memory safety defect in animation handling enables remote code execution when users visit malicious web pages. The vulnerability has been observed in active exploitation and carries moderate exploit probability.

CISA KEV Yes · 2022-02-153EPSS 0.23546 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Reported exploitation
11 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-02-15).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.23546 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Google, Chromium Animation. 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 a malicious HTML page that triggers animation code paths in the Chromium renderer.
Business
Users visiting untrusted websites face arbitrary code execution risk without additional user interaction.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I exploit the use-after-free condition to corrupt heap memory and gain control of execution flow.
Business
Attackers can achieve remote code execution within the browser sandbox, potentially escalating to system compromise.
3

Lateral reach — past segmentation narrative 3

Attacker
I distribute the malicious page through compromised sites, ads, or social engineering to maximize victim exposure.
Business
Organizations face widespread browser compromise across their user base, enabling data theft and lateral movement.
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)
  • 11 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Catalogued by Chrome (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 ChromeCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.