Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🛡️
CISA KEV · ACTIVELY EXPLOITED
HIGH severity

CVE-2021-21193 — Chrome

HIGH

CVE-2021-21193 is a high-severity (CVSS 8.8) Use After Free vulnerability. It is in CISA's Known Exploited Vulnerabilities catalog (added 2021-11-03) — treat it as actively exploited and patch now. No vendor fix is recorded yet; mitigation options are listed below.

Published
Updated
Affected
3 products
Patched
See advisory
Exploits
3 known
Exploitation data as of Oct 22, 2026 · OSV.dev, NVD, CISA KEV, FIRST.org (EPSS)

Exploitation Status

Actively exploited in the wild

  • Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2021-11-03. Federal agencies were required to remediate by 2021-11-17.
  • A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2021-21193.

EPSS Exploitation Probability

via FIRST.org ↗
10.0%probability of exploitation in next 30 days
Lower Risk+0.08%
Lower risk than most CVEs96th percentile — riskier than 96% of all scored CVEsHighest risk
6.45%12.5%18.6%24.7%21.3%10.0%Apr 26Aug 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2021-21193 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 395,249 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Description

Use after free in Blink in Google Chrome prior to 89.0.4389.90 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

Affected Products

3 products · 3 configurations
OS
debian linuxdebian
1 version
10.0
OS
fedorafedoraproject
1 version
32
Application
chromegoogle
< 89.0.4389.90
range
Exploits & PoCs
3

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Use after free in Blink in Google Chrome prior to 89.0.4389.90 allowed a…

chromereleases.googleblog.comChromeMar 2021

Use after free in Blink in Google Chrome prior to 89.0.4389.90 allowed a…

chromereleases.googleblog.comGoogle-sheetMar 2021

Use after free in Blink in Google Chrome prior to 89.0.4389.90 allowed a…

cisa.govCISANov 2021

Detection & mitigation playbook

Vulnerability

  1. Detect

    Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

  2. Remediation status

    No fixed release is recorded for CVE-2021-21193 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.

  3. Mitigate without a patch

    Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Frequently Asked Questions

Use after free in Blink in Google Chrome prior to 89.0.4389.90 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
O3 Security · Impact-Aware SCA

Is CVE-2021-21193 in your dependencies?

Find it across , including transitive dependencies.

Scan my dependencies How O3 SCA works
Actively Exploited: CVE-2021-21193: Chrome (High 8.8)