Out of bounds write in V8 in Google Chrome prior to 93.0.4577.82 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
CVE-2021-30632
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. Confidence: HIGH.
- Actively exploited in the wild (CISA-KEV)
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.8
- EG Score
- 9.0(high)
- EG Risk
- 81(Attend)EG Risk 81/100SSVC: Attend
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity90% × 45%Exploitation100% × 40%Automatability0% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 63%
- EPSS %ILE
- 99%
- KEV
- ⚠ Exploited
Published
October 8, 2021
Last Modified
October 24, 2025
Advisory Details (5)
Auto-updated Jun 1, 2026[SECURITY] Fedora 35 Update: chromium-94.0.4606.61-1.fc35 - package-announce - Fedora mailing-lists
https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/PM7MOYYHJSWLIFZ4TPJTD7MSA3HSSLV2/[SECURITY] Fedora 33 Update: chromium-94.0.4606.61-1.fc33 - package-announce - Fedora mailing-lists
https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/4DDW7HAHTS3SDVXBQUY4SURELO5D4X7R/Chrome Releases: Stable Channel Update for Desktop
https://chromereleases.googleblog.com/2021/09/stable-channel-update-for-desktop.htmlAffected Packages
(4 across 4 ecosystems)
Debian:11(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| chromium | 90.0.4430.212-1 | 93.0.4577.82-1 | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| chromium | — | 93.0.4577.82-1 | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| chromium | — | 93.0.4577.82-1 | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| chromium | — | 93.0.4577.82-1 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
All Vendor Advisories
(1)
Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.
Data Freshness Timeline
(refreshed 102× in last 7d / 414× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.
Showing the most recent 100 of 1,348 total refreshes for this CVE.
- 2026-09-08 13:17 UTCVendor advisory
- 2026-09-08 13:16 UTCGHSA enrichment
- 2026-09-08 09:29 UTCGHSA enrichment
- 2026-09-08 05:43 UTCVendor advisory
- 2026-09-08 05:42 UTCGHSA enrichment
- 2026-09-08 01:56 UTCVendor advisory
- 2026-09-08 01:56 UTCGHSA enrichment
- 2026-09-07 22:11 UTCVendor advisory
- 2026-09-07 22:11 UTCGHSA enrichment
- 2026-09-07 18:25 UTCVendor advisory
- 2026-09-07 18:25 UTCGHSA enrichment
- 2026-09-07 14:39 UTCVendor advisory
- 2026-09-07 14:39 UTCGHSA enrichment
- 2026-09-07 10:50 UTCVendor advisory
- 2026-09-07 10:49 UTCGHSA enrichment
- 2026-09-07 07:02 UTCVendor advisory
- 2026-09-07 07:02 UTCGHSA enrichment
- 2026-09-07 03:14 UTCVendor advisory
- 2026-09-07 03:14 UTCGHSA enrichment
- 2026-09-06 23:24 UTCVendor advisory
- 2026-09-06 23:24 UTCGHSA enrichment
- 2026-09-06 19:38 UTCVendor advisory
- 2026-09-06 19:38 UTCGHSA enrichment
- 2026-09-06 15:52 UTCEG score recompute
- 2026-09-06 15:52 UTCVendor advisory
Show 75 moreShow fewer
- 2026-09-06 15:52 UTCGHSA enrichment
- 2026-09-06 13:44 UTCEPSS rescore
- 2026-09-06 12:06 UTCVendor advisory
- 2026-09-06 12:05 UTCGHSA enrichment
- 2026-09-06 08:17 UTCVendor advisory
- 2026-09-06 08:17 UTCGHSA enrichment
- 2026-09-06 04:30 UTCVendor advisory
- 2026-09-06 04:30 UTCGHSA enrichment
- 2026-09-06 00:45 UTCVendor advisory
- 2026-09-06 00:45 UTCGHSA enrichment
- 2026-09-05 20:59 UTCVendor advisory
- 2026-09-05 20:59 UTCGHSA enrichment
- 2026-09-05 17:14 UTCEG score recompute
- 2026-09-05 17:14 UTCVendor advisory
- 2026-09-05 17:14 UTCGHSA enrichment
- 2026-09-05 15:25 UTCEPSS rescore
- 2026-09-05 13:28 UTCVendor advisory
- 2026-09-05 13:27 UTCGHSA enrichment
- 2026-09-05 09:41 UTCVendor advisory
- 2026-09-05 09:41 UTCGHSA enrichment
- 2026-09-05 05:55 UTCVendor advisory
- 2026-09-05 05:55 UTCGHSA enrichment
- 2026-09-05 02:09 UTCVendor advisory
- 2026-09-05 02:09 UTCGHSA enrichment
- 2026-09-04 22:23 UTCVendor advisory
- 2026-09-04 22:22 UTCGHSA enrichment
- 2026-09-04 18:36 UTCVendor advisory
- 2026-09-04 18:36 UTCGHSA enrichment
- 2026-09-04 17:38 UTCCISA KEV update
- 2026-09-04 14:47 UTCVendor advisory
- 2026-09-04 14:47 UTCGHSA enrichment
- 2026-09-04 10:57 UTCVendor advisory
- 2026-09-04 10:56 UTCGHSA enrichment
- 2026-09-04 07:09 UTCEG score recompute
- 2026-09-04 07:09 UTCVendor advisory
- 2026-09-04 07:09 UTCGHSA enrichment
- 2026-09-04 05:03 UTCEPSS rescore
- 2026-09-04 05:03 UTCEPSS rescore
- 2026-09-04 03:23 UTCVendor advisory
- 2026-09-04 03:23 UTCGHSA enrichment
- 2026-09-03 23:36 UTCVendor advisory
- 2026-09-03 23:36 UTCGHSA enrichment
- 2026-09-03 19:48 UTCVendor advisory
- 2026-09-03 19:48 UTCGHSA enrichment
- 2026-09-03 16:02 UTCVendor advisory
- 2026-09-03 16:02 UTCGHSA enrichment
- 2026-09-03 12:16 UTCVendor advisory
- 2026-09-03 12:16 UTCGHSA enrichment
- 2026-09-03 08:28 UTCVendor advisory
- 2026-09-03 08:28 UTCGHSA enrichment
- 2026-09-03 04:40 UTCVendor advisory
- 2026-09-03 04:40 UTCGHSA enrichment
- 2026-09-03 00:51 UTCVendor advisory
- 2026-09-03 00:51 UTCGHSA enrichment
- 2026-09-02 21:03 UTCVendor advisory
- 2026-09-02 21:03 UTCGHSA enrichment
- 2026-09-02 17:33 UTCCISA KEV update
- 2026-09-02 17:16 UTCEG score recompute
- 2026-09-02 17:16 UTCVendor advisory
- 2026-09-02 17:16 UTCGHSA enrichment
- 2026-09-02 14:08 UTCEPSS rescore
- 2026-09-02 13:28 UTCVendor advisory
- 2026-09-02 13:27 UTCGHSA enrichment
- 2026-09-02 09:41 UTCVendor advisory
- 2026-09-02 09:41 UTCGHSA enrichment
- 2026-09-02 05:54 UTCVendor advisory
- 2026-09-02 05:54 UTCGHSA enrichment
- 2026-09-02 02:06 UTCVendor advisory
- 2026-09-02 02:06 UTCGHSA enrichment
- 2026-09-01 22:18 UTCVendor advisory
- 2026-09-01 22:18 UTCGHSA enrichment
- 2026-09-01 18:33 UTCVendor advisory
- 2026-09-01 18:33 UTCGHSA enrichment
- 2026-09-01 14:46 UTCEG score recompute
- 2026-09-01 14:46 UTCVendor advisory
Publicly available exploits
(1 reference)Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
- Open source ↗GitHub PoCCrackerCat/CVE-2021-30632First seen Sep 28, 2021
Frequently asked(6)
What is CVE-2021-30632?
When was CVE-2021-30632 disclosed?
Is CVE-2021-30632 actively exploited?
What is the CVSS score of CVE-2021-30632?
Which products are affected by CVE-2021-30632?
How do I remediate CVE-2021-30632?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2021-30632
Is Your Infrastructure Affected by CVE-2021-30632?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.