Use after free in DOM in Google Chrome prior to 151.0.7922.173 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)
CVE-2026-76021
HIGHCVSS · not yet scored8.8Trending — 3 sources updated this week
EchelonGraph scoreLOW confidence
Google's Chromium security team rated this High in the advisory text — the exact wording is "(Chromium security severity: High)". Chromium's CNA does not publish a CVSS vector, and NVD has not yet analysed this record, so there is no CVSS v3.1, v4.0 or v2.0 base score for it from any source. EchelonGraph publishes 8.8 (HIGH), derived from the VENDOR'S OWN SEVERITY BAND — not from a CVSS vector. That number is calibrated, not assumed: across 1101 Chromium CVEs that NVD has since scored, a Chromium "High" carried a median CVSS v3 base of 8.8. This score is provisional and will be superseded the moment any source publishes a real CVSS base. Confidence: LOW.
Sources: vendor_prose:chromium
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: —CVSS v2: —Exploit: None knownExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- —
- Vendor severity
- HIGHper Google (Chromium)Vendor's own band, not a CVSS rating — advisory text: (Chromium security severity: High)
- EG Score
- 8.8(low)
- EG Risk
- 44(Track)EG Risk 44/100SSVC: Track
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 computedSeverity88% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
August 20, 2026
Last Modified
August 20, 2026
References (2)
- chrome-cve-admin@googlehttps://chromereleases.googleblog.com/2026/08/stable-channel-update-for-desktop_0404570826.html
- chrome-cve-admin@googlehttps://issues.chromium.org/issues/541854084
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 3× in last 7d / 3× 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.
- 2026-08-20 21:21 UTCNVD update
- 2026-08-20 20:57 UTCEG score recompute
- 2026-08-20 20:56 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(3)
What is CVE-2026-76021?
CVE-2026-76021 is a high vulnerability published on August 20, 2026. Use after free in DOM in Google Chrome prior to 151.0.7922.173 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)
When was CVE-2026-76021 disclosed?
CVE-2026-76021 was first published in the National Vulnerability Database on August 20, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
How do I remediate CVE-2026-76021?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-76021, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-76021
Is Your Infrastructure Affected by CVE-2026-76021?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.