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

Google Chromium WebGL vulnerability

Use-after-free vulnerability in Chromium WebGL allows remote attackers to exploit heap corruption through crafted HTML pages, affecting multiple browsers including Chrome, Edge, and Opera.

Verdict

Today item — known-exploited.

A use-after-free flaw in WebGL rendering enables remote code execution via malicious web content. The vulnerability has been exploited in the wild, posing significant risk to users of Chromium-based browsers.

CISA KEV Yes · 2021-11-033EPSS 0.07367 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Reported exploitation
3 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 2021-11-03).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.07367 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Google, Chromium WebGL. 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 containing WebGL code that triggers a use-after-free condition in the rendering engine.
Business
Users visiting the attacker's webpage or a compromised site face potential arbitrary code execution with browser privileges.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I host the exploit on a website or distribute it through watering hole attacks targeting specific user populations.
Business
Widespread browser compromise across user base, enabling data theft, credential harvesting, or lateral movement to endpoints.
3

Lateral reach — past segmentation narrative 3

Attacker
I leverage heap corruption to bypass security mitigations and achieve reliable code execution within the browser sandbox.
Business
Attackers gain foothold for further exploitation, potentially escaping sandbox to compromise the underlying operating system.
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)
  • 3 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.