Inappropriate implementation in Memory in Google Chrome prior to 94.0.4606.71 allowed a remote attacker to obtain potentially sensitive information from process memory via a crafted HTML page.
CVE-2021-37976
“▲” 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 6.5 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 6.5 MEDIUM under GitHub Security Advisory CVSS. Confidence: HIGH.
- Actively exploited in the wild (CISA-KEV) — the reason this is sooner than the SSVC decision on this page at every mission impact level
A fix is available — apply it.
- CVSS v3
- 6.5
- EG Score
- 9.0CRITICALhigh confidence
- EG Risk
- 69EG Risk 69/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)Severity65% × 45%Impact severity (EG Severity): CVSS 6.5 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 or medium mission impact; Attend at high (mission-essential systems).Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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 or medium mission impact and sooner than that at high. - EPSS PROB
- 20%
- EPSS %ILE
- 97th
- 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 6.5 MEDIUM.
- EG Severity
- 6.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 20% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-22). 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 Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 14 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)14 days if the affected system is publicly exposed; 14 days if it is not.
In CISA KEV yes (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (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-37976
Published
October 8, 2021
Last Modified
October 24, 2025
Advisory Details (6)
Auto-updated Oct 20, 2026[SECURITY] Fedora 35 Update: chromium-94.0.4606.81-1.fc35 - package-announce - Fedora mailing-lists
https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/FRFXUDH46PFVE75VQVWY6PYY5DK3S2XT/[SECURITY] Fedora 34 Update: chromium-94.0.4606.81-1.fc34 - package-announce - Fedora mailing-lists
https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/D63JZ3ROXCUHP4CFWDHCPZNTGET7T34R/Chrome Releases: Stable Channel Update for Desktop
https://chromereleases.googleblog.com/2021/09/stable-channel-update-for-desktop_30.html[SECURITY] [DSA 5046-1] chromium security update
https://www.debian.org/security/2022/dsa-5046[SECURITY] Fedora 33 Update: chromium-94.0.4606.81-1.fc33 - package-announce - Fedora mailing-lists
https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/RNARCF5HEZK7GJXZRN5TQ45AQDCRM2WO/Vendor Advisories for CVE-2021-37976(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(4 across 4 ecosystems)
Debian:11(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| chromium | 90.0.4430.212-1, 93.0.4577.82-1 |
| — |
Debian:12(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| chromium | — |
| — |
Debian:13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| chromium | — |
| — |
Debian:14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| chromium | — |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 28× in last 7d / 302× 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,878 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,778 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-10-23 16:28 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-10-23 08:35 UTCEG score recompute
- 2026-10-23 08:35 UTCVendor advisory
- 2026-10-23 08:34 UTCGHSA enrichmentGHSA-c9r9-7qcg-7h37 · GitHub CVSS 6.5
- 2026-10-22 16:29 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-10-22 10:26 UTCEG score recompute
- 2026-10-22 10:26 UTCVendor advisory
- 2026-10-22 10:26 UTCGHSA enrichmentGHSA-c9r9-7qcg-7h37 · GitHub CVSS 6.5
- 2026-10-21 16:28 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-10-21 12:18 UTCEG score recompute
- 2026-10-21 12:18 UTCVendor advisory
- 2026-10-21 12:18 UTCGHSA enrichmentGHSA-c9r9-7qcg-7h37 · GitHub CVSS 6.5
- 2026-10-20 16:28 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-10-20 14:10 UTCEG score recompute
- 2026-10-20 14:09 UTCGHSA enrichmentGHSA-c9r9-7qcg-7h37 · GitHub CVSS 6.5
- 2026-10-19 16:28 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-10-19 16:01 UTCVendor advisory
- 2026-10-19 16:00 UTCGHSA enrichmentGHSA-c9r9-7qcg-7h37 · GitHub CVSS 6.5
- 2026-10-18 17:52 UTCEG score recompute
- 2026-10-18 17:52 UTCVendor advisory
- 2026-10-18 17:52 UTCGHSA enrichmentGHSA-c9r9-7qcg-7h37 · GitHub CVSS 6.5
- 2026-10-18 08:57 UTCEG score recompute
- 2026-10-17 19:44 UTCEG score recompute
- 2026-10-17 19:44 UTCVendor advisory
- 2026-10-17 19:44 UTCGHSA enrichmentGHSA-c9r9-7qcg-7h37 · GitHub CVSS 6.5
Show 75 moreShow fewer
- 2026-10-17 16:29 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-10-16 21:35 UTCEG score recompute
- 2026-10-16 21:35 UTCGHSA enrichmentGHSA-c9r9-7qcg-7h37 · GitHub CVSS 6.5
- 2026-10-16 16:33 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-10-15 23:28 UTCEG score recompute
- 2026-10-15 23:28 UTCGHSA enrichmentGHSA-c9r9-7qcg-7h37 · GitHub CVSS 6.5
- 2026-10-15 16:28 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-10-15 01:20 UTCEG score recompute
- 2026-10-15 01:20 UTCGHSA enrichmentGHSA-c9r9-7qcg-7h37 · GitHub CVSS 6.5
- 2026-10-14 16:28 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-10-14 03:10 UTCEG score recompute
- 2026-10-14 03:10 UTCGHSA enrichmentGHSA-c9r9-7qcg-7h37 · GitHub CVSS 6.5
- 2026-10-13 16:28 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-10-13 04:59 UTCVendor advisory
- 2026-10-13 04:59 UTCGHSA enrichmentGHSA-c9r9-7qcg-7h37 · GitHub CVSS 6.5
- 2026-10-12 19:12 UTCEG score recompute
- 2026-10-12 06:51 UTCVendor advisory
- 2026-10-12 06:51 UTCGHSA enrichmentGHSA-c9r9-7qcg-7h37 · GitHub CVSS 6.5
- 2026-10-12 02:54 UTCVendor advisory
- 2026-10-12 02:54 UTCGHSA enrichmentGHSA-c9r9-7qcg-7h37 · GitHub CVSS 6.5
- 2026-10-11 22:56 UTCEG score recompute
- 2026-10-11 22:56 UTCVendor advisory
- 2026-10-11 22:56 UTCGHSA enrichmentGHSA-c9r9-7qcg-7h37 · GitHub CVSS 6.5
- 2026-10-11 18:58 UTCEG score recompute
- 2026-10-11 18:58 UTCVendor advisory
- 2026-10-11 18:58 UTCGHSA enrichmentGHSA-c9r9-7qcg-7h37 · GitHub CVSS 6.5
- 2026-10-11 15:03 UTCEG score recompute
- 2026-10-11 15:03 UTCVendor advisory
- 2026-10-11 15:03 UTCGHSA enrichmentGHSA-c9r9-7qcg-7h37 · GitHub CVSS 6.5
- 2026-10-11 13:43 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-10-11 11:07 UTCVendor advisory
- 2026-10-11 11:06 UTCGHSA enrichmentGHSA-c9r9-7qcg-7h37 · GitHub CVSS 6.5
- 2026-10-11 07:09 UTCVendor advisory
- 2026-10-11 07:09 UTCGHSA enrichmentGHSA-c9r9-7qcg-7h37 · GitHub CVSS 6.5
- 2026-10-11 03:13 UTCVendor advisory
- 2026-10-11 03:13 UTCGHSA enrichmentGHSA-c9r9-7qcg-7h37 · GitHub CVSS 6.5
- 2026-10-10 23:17 UTCEG score recompute
- 2026-10-10 23:17 UTCVendor advisory
- 2026-10-10 23:17 UTCGHSA enrichmentGHSA-c9r9-7qcg-7h37 · GitHub CVSS 6.5
- 2026-10-10 19:56 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-10-10 19:21 UTCGHSA enrichmentGHSA-c9r9-7qcg-7h37 · GitHub CVSS 6.5
- 2026-10-10 15:26 UTCGHSA enrichmentGHSA-c9r9-7qcg-7h37 · GitHub CVSS 6.5
- 2026-10-10 11:30 UTCVendor advisory
- 2026-10-10 11:30 UTCGHSA enrichmentGHSA-c9r9-7qcg-7h37 · GitHub CVSS 6.5
- 2026-10-10 07:34 UTCVendor advisory
- 2026-10-10 07:34 UTCGHSA enrichmentGHSA-c9r9-7qcg-7h37 · GitHub CVSS 6.5
- 2026-10-10 03:38 UTCVendor advisory
- 2026-10-10 03:38 UTCGHSA enrichmentGHSA-c9r9-7qcg-7h37 · GitHub CVSS 6.5
- 2026-10-09 23:43 UTCEG score recompute
- 2026-10-09 23:43 UTCVendor advisory
- 2026-10-09 23:43 UTCGHSA enrichmentGHSA-c9r9-7qcg-7h37 · GitHub CVSS 6.5
- 2026-10-09 20:04 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-10-09 19:48 UTCVendor advisory
- 2026-10-09 19:48 UTCGHSA enrichmentGHSA-c9r9-7qcg-7h37 · GitHub CVSS 6.5
- 2026-10-09 15:52 UTCVendor advisory
- 2026-10-09 15:52 UTCGHSA enrichmentGHSA-c9r9-7qcg-7h37 · GitHub CVSS 6.5
- 2026-10-09 11:56 UTCVendor advisory
- 2026-10-09 11:56 UTCGHSA enrichmentGHSA-c9r9-7qcg-7h37 · GitHub CVSS 6.5
- 2026-10-09 07:59 UTCVendor advisory
- 2026-10-09 07:59 UTCGHSA enrichmentGHSA-c9r9-7qcg-7h37 · GitHub CVSS 6.5
- 2026-10-09 04:03 UTCVendor advisory
- 2026-10-09 04:03 UTCGHSA enrichmentGHSA-c9r9-7qcg-7h37 · GitHub CVSS 6.5
- 2026-10-09 00:07 UTCVendor advisory
- 2026-10-09 00:07 UTCGHSA enrichmentGHSA-c9r9-7qcg-7h37 · GitHub CVSS 6.5
- 2026-10-08 20:12 UTCEG score recompute
- 2026-10-08 20:12 UTCVendor advisory
- 2026-10-08 20:11 UTCGHSA enrichmentGHSA-c9r9-7qcg-7h37 · GitHub CVSS 6.5
- 2026-10-08 16:39 UTCEPSS rescoreEPSS 20% · 97th percentile
- 2026-10-08 16:16 UTCVendor advisory
- 2026-10-08 16:15 UTCGHSA enrichmentGHSA-c9r9-7qcg-7h37 · GitHub CVSS 6.5
- 2026-10-08 12:16 UTCVendor advisory
- 2026-10-08 12:16 UTCGHSA enrichmentGHSA-c9r9-7qcg-7h37 · GitHub CVSS 6.5
- 2026-10-08 08:20 UTCVendor advisory
- 2026-10-08 08:19 UTCGHSA enrichmentGHSA-c9r9-7qcg-7h37 · GitHub CVSS 6.5
- 2026-10-08 04:24 UTCVendor advisory
Related CVEs(same CWE)
Same CWE
10 shownCWE-862
Frequently asked(6)
What is CVE-2021-37976?
When was the CVE record for CVE-2021-37976 published?
Is CVE-2021-37976 actively exploited?
What is the CVSS score of CVE-2021-37976?
Which products are affected by CVE-2021-37976?
How do I remediate CVE-2021-37976?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2021-37976
Is Your Infrastructure Affected by CVE-2021-37976?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.