Threats / Google / CVE-2021-21193
CVE-2021-21193
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Google Chromium Blink vulnerability
Use-after-free vulnerability in Chromium Blink allows remote attackers to exploit heap corruption through crafted HTML, affecting multiple browsers including Chrome, Edge, and Opera.
Verdict
Today item — known-exploited.
A use-after-free flaw in Chromium Blink enables remote code execution via malicious web content. The vulnerability has been exploited in the wild, posing significant risk to users of affected browsers.
CISA KEV Yes · 2021-11-034EPSS 0.0987 (verify live)5CVSS 8.8 (CISA)3CISA SSVC Exploitation: active · Automatable: no · Impact: total3
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
2 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).
Probability (EPSS)
EPSS 0.0987 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 8.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) · Affected: Google, Chromium Blink. Confirm exact fixed builds in the vendor advisory.CVSS — CISA-assigned via the ADP container (CVE.org), version 3.1; the CNA left no metrics, so CISA's own score is used ahead of NVD.
Weakness (CWE)
Mapped to CWE-416 Use After Free — weakness family: Memory safety.CWE assignment from the public NVD record (may be stale); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: no · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 232 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution 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 board1
Front door — unauthenticated access narrative 1
Attacker
I craft a malicious HTML page that triggers improper memory management in Blink's rendering engine.
Business
Users visiting attacker-controlled or compromised websites face arbitrary code execution within browser context.
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 steal credentials, session tokens, and sensitive data from users' browsing sessions.
3
Lateral reach — past segmentation narrative 3
Attacker
I leverage the compromised browser process to establish persistence or pivot to the underlying system.
Business
Organizations face data breaches, malware distribution, and potential lateral movement within corporate 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