CVE-2021-21224

CRITICALNVD 8.89.0
EchelonGraph scoreHIGH confidence

“▲” beside the score: it is higher than NVD's CVSS score.

Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2021-11-03), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 8.8 retained for reference. The 9.0 is the floor for confirmed exploitation, not an impact rating: this CVE's impact severity (EG Severity) is CVSS 8.8 HIGH under GitHub Security Advisory CVSS. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: CISA Known Exploited Vulnerabilities catalog, EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this weekExploited in the wild

Also known asEUVD-2021-8615 (ENISA EUVD) · GHSA-g2xr-gx3h-vpc9 (GitHub Security Advisories)Source: ENISA EUVD

9.0EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV) — the reason this is sooner than the SSVC decision on this page at low or medium mission impact
CISA-KEV: ExploitedEPSS PROB: 84%CVSS: 8.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Type confusion in V8 in Google Chrome prior to 90.0.4430.85 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page.

CVSS v3
8.8
EG Score
9.0CRITICALhigh confidence
EG Risk
80
EG Risk 80/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity88% × 45%
Impact severity (EG Severity): CVSS 8.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation100% × 40%
Fixed at 100% for a CISA KEV listing: EchelonGraph's rule.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Attend at medium and Act at high mission impact.
Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact.
EPSS PROB
84%
EPSS %ILE
99th
KEV
⚠ Exploited

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.0): severity, escalated by confirmed exploitation. This CVE's 9.0 is the CISA KEV floor for confirmed exploitation, not an impact rating: its impact severity (EG Severity) is CVSS 8.8 HIGH.

EG Severity
8.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
84% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
CISA KEV and EG-KEV Tier 1 (exploited in the wild)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Attend at medium mission impactTrack at low, Attend at medium and Act at high mission impact.CISA BOD 26-04: 3 days & forensic triage if the affected system is publicly exposed; 14 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Attend at medium and Act at high mission impact.

A fix is available. Apply it within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact.

Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days & forensic triage if the affected system is publicly exposed; 14 days if it is not.

The score's inputs: In CISA KEV yes (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

CISA required action“Apply updates per vendor instructions.”

Quoted verbatim from CISA's Known Exploited Vulnerabilities catalog. CISA directs it at US federal civilian executive branch agencies under Binding Operational Directive (BOD) 26-04, which replaced BOD 22-01 on 10 June 2026; it is not EchelonGraph's advice. CISA's notes: https://nvd.nist.gov/vuln/detail/CVE-2021-21224

Published

April 26, 2021

Last Modified

October 24, 2025

Advisory Details (7)

Auto-updated Oct 26, 2026
⚠️ Actively exploited (CISA KEV, CISA Vulnrichment). Patch available.
Web page

[SECURITY] Fedora 32 Update: chromium-90.0.4430.93-1.fc32 - package-announce - Fedora mailing-lists

https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/EAJ42L4JFPBJATCZ7MOZQTUDGV4OEHHG/
Web page

Chrome Releases: Stable Channel Update for Desktop

https://chromereleases.googleblog.com/2021/04/stable-channel-update-for-desktop_20.html
Web page

[SECURITY] [DSA 4906-1] chromium security update

https://www.debian.org/security/2021/dsa-4906
Web page

Chromium, Google Chrome: Multiple vulnerabilities (GLSA 202104-08) — Gentoo security

https://security.gentoo.org/glsa/202104-08
Web page

[SECURITY] Fedora 34 Update: chromium-90.0.4430.93-1.fc34 - package-announce - Fedora mailing-lists

https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/VUZBGKGVZADNA3I24NVG7HAYYUTOSN5A/
Web page

[SECURITY] Fedora 33 Update: chromium-90.0.4430.93-1.fc33 - package-announce - Fedora mailing-lists

https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/U3GZ42MYPGD35V652ZPVPYYS7A7LVXVY/

Vendor Advisories for CVE-2021-21224(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(5 across 5 ecosystems)
Debian:10(1)
PackageVulnerable rangeFix by version rangeDependents
chromium73.0.3683.75-1 ... 90.0.4430.72-1 (64 versions)
  • every version up to 90.0.4430.85-1~deb10u1: fixed in 90.0.4430.85-1~deb10u1
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
chromium—
  • every version up to 90.0.4430.85-1: fixed in 90.0.4430.85-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
chromium—
  • every version up to 90.0.4430.85-1: fixed in 90.0.4430.85-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
chromium—
  • every version up to 90.0.4430.85-1: fixed in 90.0.4430.85-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
chromium—
  • every version up to 90.0.4430.85-1: fixed in 90.0.4430.85-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 21× in last 7d / 171× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 1,727 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 1,627 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 05:31 UTCEG score recompute
  2. 2026-11-02 05:31 UTCVendor advisory
  3. 2026-11-02 05:31 UTCGHSA enrichmentGHSA-g2xr-gx3h-vpc9 · GitHub severity HIGH · GitHub CVSS 8.8
  4. 2026-11-01 03:11 UTCEG score recompute
  5. 2026-11-01 03:11 UTCVendor advisory
  6. 2026-11-01 03:11 UTCGHSA enrichmentGHSA-g2xr-gx3h-vpc9 · GitHub severity HIGH · GitHub CVSS 8.8
  7. 2026-10-31 16:28 UTCEPSS rescoreEPSS 84% · 99th percentile
  8. 2026-10-31 00:51 UTCEG score recompute
  9. 2026-10-31 00:51 UTCVendor advisory
  10. 2026-10-31 00:51 UTCGHSA enrichmentGHSA-g2xr-gx3h-vpc9 · GitHub severity HIGH · GitHub CVSS 8.8
  11. 2026-10-29 22:31 UTCEG score recompute
  12. 2026-10-29 22:31 UTCVendor advisory
  13. 2026-10-29 22:31 UTCGHSA enrichmentGHSA-g2xr-gx3h-vpc9 · GitHub severity HIGH · GitHub CVSS 8.8
  14. 2026-10-29 16:29 UTCEPSS rescoreEPSS 84% · 99th percentile
  15. 2026-10-28 20:11 UTCEG score recompute
  16. 2026-10-28 20:11 UTCGHSA enrichmentGHSA-g2xr-gx3h-vpc9 · GitHub severity HIGH · GitHub CVSS 8.8
  17. 2026-10-27 17:52 UTCEG score recompute
  18. 2026-10-27 17:52 UTCVendor advisory
  19. 2026-10-27 17:52 UTCGHSA enrichmentGHSA-g2xr-gx3h-vpc9 · GitHub severity HIGH · GitHub CVSS 8.8
  20. 2026-10-27 16:28 UTCEPSS rescoreEPSS 84% · 99th percentile
  21. 2026-10-26 15:32 UTCGHSA enrichmentGHSA-g2xr-gx3h-vpc9 · GitHub severity HIGH · GitHub CVSS 8.8
  22. 2026-10-25 18:35 UTCEG score recompute
  23. 2026-10-25 16:28 UTCEPSS rescoreEPSS 84% · 99th percentile
  24. 2026-10-25 13:13 UTCEG score recompute
  25. 2026-10-25 13:13 UTCVendor advisory
Show 75 more
  1. 2026-10-25 13:13 UTCGHSA enrichmentGHSA-g2xr-gx3h-vpc9 · GitHub severity HIGH · GitHub CVSS 8.8
  2. 2026-10-24 16:28 UTCEPSS rescoreEPSS 84% · 99th percentile
  3. 2026-10-24 10:53 UTCEG score recompute
  4. 2026-10-24 10:53 UTCGHSA enrichmentGHSA-g2xr-gx3h-vpc9 · GitHub severity HIGH · GitHub CVSS 8.8
  5. 2026-10-23 08:32 UTCEG score recompute
  6. 2026-10-23 08:32 UTCVendor advisory
  7. 2026-10-23 08:32 UTCGHSA enrichmentGHSA-g2xr-gx3h-vpc9 · GitHub severity HIGH · GitHub CVSS 8.8
  8. 2026-10-22 16:29 UTCEPSS rescoreEPSS 84% · 99th percentile
  9. 2026-10-22 06:11 UTCEG score recompute
  10. 2026-10-22 06:11 UTCVendor advisory
  11. 2026-10-22 06:11 UTCGHSA enrichmentGHSA-g2xr-gx3h-vpc9 · GitHub severity HIGH · GitHub CVSS 8.8
  12. 2026-10-21 16:28 UTCEPSS rescoreEPSS 84% · 99th percentile
  13. 2026-10-21 03:50 UTCEG score recompute
  14. 2026-10-21 03:50 UTCGHSA enrichmentGHSA-g2xr-gx3h-vpc9 · GitHub severity HIGH · GitHub CVSS 8.8
  15. 2026-10-20 01:29 UTCEG score recompute
  16. 2026-10-20 01:29 UTCVendor advisory
  17. 2026-10-20 01:29 UTCGHSA enrichmentGHSA-g2xr-gx3h-vpc9 · GitHub severity HIGH · GitHub CVSS 8.8
  18. 2026-10-19 16:28 UTCEPSS rescoreEPSS 84% · 99th percentile
  19. 2026-10-18 23:09 UTCEG score recompute
  20. 2026-10-18 23:09 UTCVendor advisory
  21. 2026-10-18 23:09 UTCGHSA enrichmentGHSA-g2xr-gx3h-vpc9 · GitHub severity HIGH · GitHub CVSS 8.8
  22. 2026-10-18 09:11 UTCEG score recompute
  23. 2026-10-17 20:47 UTCEG score recompute
  24. 2026-10-17 20:47 UTCVendor advisory
  25. 2026-10-17 20:47 UTCGHSA enrichmentGHSA-g2xr-gx3h-vpc9 · GitHub severity HIGH · GitHub CVSS 8.8
  26. 2026-10-16 18:26 UTCEG score recompute
  27. 2026-10-16 18:26 UTCGHSA enrichmentGHSA-g2xr-gx3h-vpc9 · GitHub severity HIGH · GitHub CVSS 8.8
  28. 2026-10-15 16:05 UTCEG score recompute
  29. 2026-10-15 16:04 UTCGHSA enrichmentGHSA-g2xr-gx3h-vpc9 · GitHub severity HIGH · GitHub CVSS 8.8
  30. 2026-10-14 16:28 UTCEPSS rescoreEPSS 84% · 99th percentile
  31. 2026-10-14 13:43 UTCEG score recompute
  32. 2026-10-14 13:43 UTCGHSA enrichmentGHSA-g2xr-gx3h-vpc9 · GitHub severity HIGH · GitHub CVSS 8.8
  33. 2026-10-13 11:22 UTCVendor advisory
  34. 2026-10-13 11:22 UTCGHSA enrichmentGHSA-g2xr-gx3h-vpc9 · GitHub severity HIGH · GitHub CVSS 8.8
  35. 2026-10-12 19:25 UTCEG score recompute
  36. 2026-10-12 08:58 UTCVendor advisory
  37. 2026-10-12 08:58 UTCGHSA enrichmentGHSA-g2xr-gx3h-vpc9 · GitHub severity HIGH · GitHub CVSS 8.8
  38. 2026-10-12 04:43 UTCVendor advisory
  39. 2026-10-12 04:43 UTCGHSA enrichmentGHSA-g2xr-gx3h-vpc9 · GitHub severity HIGH · GitHub CVSS 8.8
  40. 2026-10-12 00:26 UTCEG score recompute
  41. 2026-10-12 00:26 UTCVendor advisory
  42. 2026-10-12 00:25 UTCGHSA enrichmentGHSA-g2xr-gx3h-vpc9 · GitHub severity HIGH · GitHub CVSS 8.8
  43. 2026-10-11 20:09 UTCEG score recompute
  44. 2026-10-11 20:09 UTCVendor advisory
  45. 2026-10-11 20:09 UTCGHSA enrichmentGHSA-g2xr-gx3h-vpc9 · GitHub severity HIGH · GitHub CVSS 8.8
  46. 2026-10-11 15:52 UTCEG score recompute
  47. 2026-10-11 15:52 UTCVendor advisory
  48. 2026-10-11 15:52 UTCGHSA enrichmentGHSA-g2xr-gx3h-vpc9 · GitHub severity HIGH · GitHub CVSS 8.8
  49. 2026-10-11 11:38 UTCEG score recompute
  50. 2026-10-11 11:38 UTCVendor advisory
  51. 2026-10-11 11:38 UTCGHSA enrichmentGHSA-g2xr-gx3h-vpc9 · GitHub severity HIGH · GitHub CVSS 8.8
  52. 2026-10-11 07:24 UTCVendor advisory
  53. 2026-10-11 07:23 UTCGHSA enrichmentGHSA-g2xr-gx3h-vpc9 · GitHub severity HIGH · GitHub CVSS 8.8
  54. 2026-10-11 03:10 UTCVendor advisory
  55. 2026-10-11 03:09 UTCGHSA enrichmentGHSA-g2xr-gx3h-vpc9 · GitHub severity HIGH · GitHub CVSS 8.8
  56. 2026-10-10 22:55 UTCVendor advisory
  57. 2026-10-10 22:55 UTCGHSA enrichmentGHSA-g2xr-gx3h-vpc9 · GitHub severity HIGH · GitHub CVSS 8.8
  58. 2026-10-10 18:40 UTCGHSA enrichmentGHSA-g2xr-gx3h-vpc9 · GitHub severity HIGH · GitHub CVSS 8.8
  59. 2026-10-10 14:26 UTCVendor advisory
  60. 2026-10-10 14:26 UTCGHSA enrichmentGHSA-g2xr-gx3h-vpc9 · GitHub severity HIGH · GitHub CVSS 8.8
  61. 2026-10-10 10:12 UTCVendor advisory
  62. 2026-10-10 10:12 UTCGHSA enrichmentGHSA-g2xr-gx3h-vpc9 · GitHub severity HIGH · GitHub CVSS 8.8
  63. 2026-10-10 05:57 UTCVendor advisory
  64. 2026-10-10 05:56 UTCGHSA enrichmentGHSA-g2xr-gx3h-vpc9 · GitHub severity HIGH · GitHub CVSS 8.8
  65. 2026-10-10 01:42 UTCVendor advisory
  66. 2026-10-10 01:42 UTCGHSA enrichmentGHSA-g2xr-gx3h-vpc9 · GitHub severity HIGH · GitHub CVSS 8.8
  67. 2026-10-09 21:28 UTCEG score recompute
  68. 2026-10-09 21:28 UTCVendor advisory
  69. 2026-10-09 21:28 UTCGHSA enrichmentGHSA-g2xr-gx3h-vpc9 · GitHub severity HIGH · GitHub CVSS 8.8
  70. 2026-10-09 20:04 UTCEPSS rescoreEPSS 84% · 99th percentile
  71. 2026-10-09 17:14 UTCVendor advisory
  72. 2026-10-09 17:14 UTCGHSA enrichmentGHSA-g2xr-gx3h-vpc9 · GitHub severity HIGH · GitHub CVSS 8.8
  73. 2026-10-09 13:00 UTCVendor advisory
  74. 2026-10-09 13:00 UTCGHSA enrichmentGHSA-g2xr-gx3h-vpc9 · GitHub severity HIGH · GitHub CVSS 8.8
  75. 2026-10-09 08:45 UTCVendor advisory

Frequently asked(6)

What is CVE-2021-21224?
CVE-2021-21224 is a critical-severity vulnerability; its CVE record was published on April 26, 2021. Type confusion in V8 in Google Chrome prior to 90.0.4430.85 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page.
When was the CVE record for CVE-2021-21224 published?
The CVE record for CVE-2021-21224 was published on April 26, 2021. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 24, 2025; the record at its source may have been updated since.
Is CVE-2021-21224 actively exploited?
Yes. CISA added CVE-2021-21224 to the Known Exploited Vulnerabilities catalog on November 3, 2021, affecting Google Chromium V8. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. A fix is available. Apply it.
What is the CVSS score of CVE-2021-21224?
CVE-2021-21224 has a CVSS v3 base score of 8.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0 (CRITICAL).
Which products are affected by CVE-2021-21224?
CVE-2021-21224 affects Google Chromium V8. The affected packages EchelonGraph has on record, with version ranges, are listed in the Affected Packages section of this page.
How do I remediate CVE-2021-21224?
A fix for CVE-2021-21224 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2021-21224 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2021-21224

Explore →

Is Your Infrastructure Affected by CVE-2021-21224?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.