Use after free in DNS in Google Chrome prior to 151.0.7922.72 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: Low)
CVE-2026-17924
Score 9.6 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-30. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.6; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.6
- Vendor severity
- LOWper Google (Chromium)Vendor's own band, not a CVSS rating — advisory text: (Chromium security severity: Low)
- EG Score
- 9.6(medium)
- EG Risk
- 43(Track)EG Risk 43/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 computedSeverity96% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 17%
- KEV
- Not listed
Published
July 30, 2026
Last Modified
August 3, 2026
Advisory Details (2)
Auto-updated Aug 23, 2026Chrome Releases: Stable Channel Update for Desktop
https://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_0887107924.htmlVendor Advisories for CVE-2026-17924(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 | Fixed in | Dependents |
|---|---|---|---|
| chromium | 100.0.4896.127-1 ... 99.0.4844.84-1~deb11u1 (500 versions) | — | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| chromium | 113.0.5672.126-1 ... 151.0.7922.47-1 (394 versions) | 151.0.7922.71-1~deb12u1 | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| chromium | 138.0.7204.183-1 ... 151.0.7922.71-1~deb12u1 (160 versions) | 151.0.7922.71-1~deb13u1 | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| chromium | 138.0.7204.183-1 ... 151.0.7922.71-1~deb13u1 (162 versions) | — | — |
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 70× in last 7d / 353× 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 363 total refreshes for this CVE.
- 2026-08-30 06:56 UTCVendor advisory
- 2026-08-30 06:56 UTCGHSA enrichment
- 2026-08-30 02:51 UTCEG score recompute
- 2026-08-30 02:51 UTCVendor advisory
- 2026-08-30 02:51 UTCGHSA enrichment
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 22:48 UTCEG score recompute
- 2026-08-29 22:48 UTCVendor advisory
- 2026-08-29 22:48 UTCGHSA enrichment
- 2026-08-28 21:41 UTCEPSS rescore
- 2026-08-28 00:58 UTCVendor advisory
- 2026-08-28 00:58 UTCGHSA enrichment
- 2026-08-27 20:50 UTCEG score recompute
- 2026-08-27 20:50 UTCVendor advisory
- 2026-08-27 20:50 UTCGHSA enrichment
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-27 13:10 UTCVendor advisory
- 2026-08-27 13:10 UTCGHSA enrichment
- 2026-08-27 08:59 UTCVendor advisory
- 2026-08-27 08:59 UTCGHSA enrichment
- 2026-08-27 03:40 UTCVendor advisory
- 2026-08-27 03:40 UTCGHSA enrichment
- 2026-08-26 23:38 UTCVendor advisory
- 2026-08-26 23:38 UTCGHSA enrichment
- 2026-08-26 19:35 UTCVendor advisory
Show 75 moreShow fewer
- 2026-08-26 19:35 UTCGHSA enrichment
- 2026-08-26 14:53 UTCEG score recompute
- 2026-08-26 14:53 UTCVendor advisory
- 2026-08-26 14:53 UTCGHSA enrichment
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-26 10:50 UTCVendor advisory
- 2026-08-26 10:50 UTCGHSA enrichment
- 2026-08-26 06:47 UTCVendor advisory
- 2026-08-26 06:47 UTCGHSA enrichment
- 2026-08-26 02:29 UTCVendor advisory
- 2026-08-26 02:29 UTCGHSA enrichment
- 2026-08-25 22:26 UTCVendor advisory
- 2026-08-25 22:26 UTCGHSA enrichment
- 2026-08-25 18:23 UTCVendor advisory
- 2026-08-25 18:23 UTCGHSA enrichment
- 2026-08-25 14:20 UTCEG score recompute
- 2026-08-25 14:20 UTCVendor advisory
- 2026-08-25 14:20 UTCGHSA enrichment
- 2026-08-25 13:48 UTCEPSS rescore
- 2026-08-25 10:01 UTCVendor advisory
- 2026-08-25 10:01 UTCGHSA enrichment
- 2026-08-25 05:58 UTCVendor advisory
- 2026-08-25 05:58 UTCGHSA enrichment
- 2026-08-25 01:56 UTCGHSA enrichment
- 2026-08-24 21:53 UTCVendor advisory
- 2026-08-24 21:53 UTCGHSA enrichment
- 2026-08-24 17:50 UTCEG score recompute
- 2026-08-24 17:50 UTCVendor advisory
- 2026-08-24 17:50 UTCGHSA enrichment
- 2026-08-24 13:33 UTCVendor advisory
- 2026-08-24 13:33 UTCGHSA enrichment
- 2026-08-24 09:30 UTCVendor advisory
- 2026-08-24 09:30 UTCGHSA enrichment
- 2026-08-24 05:26 UTCVendor advisory
- 2026-08-24 05:26 UTCGHSA enrichment
- 2026-08-24 01:23 UTCVendor advisory
- 2026-08-24 01:23 UTCGHSA enrichment
- 2026-08-23 21:19 UTCVendor advisory
- 2026-08-23 21:19 UTCGHSA enrichment
- 2026-08-23 17:16 UTCVendor advisory
- 2026-08-23 17:16 UTCGHSA enrichment
- 2026-08-23 13:12 UTCVendor advisory
- 2026-08-23 13:12 UTCGHSA enrichment
- 2026-08-23 09:03 UTCVendor advisory
- 2026-08-23 09:03 UTCGHSA enrichment
- 2026-08-23 05:00 UTCVendor advisory
- 2026-08-23 05:00 UTCGHSA enrichment
- 2026-08-23 00:56 UTCEG score recompute
- 2026-08-23 00:56 UTCVendor advisory
- 2026-08-23 00:56 UTCGHSA enrichment
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 20:53 UTCVendor advisory
- 2026-08-22 20:53 UTCGHSA enrichment
- 2026-08-22 16:50 UTCVendor advisory
- 2026-08-22 16:50 UTCGHSA enrichment
- 2026-08-22 12:47 UTCVendor advisory
- 2026-08-22 12:47 UTCGHSA enrichment
- 2026-08-22 08:43 UTCVendor advisory
- 2026-08-22 08:43 UTCGHSA enrichment
- 2026-08-22 04:40 UTCVendor advisory
- 2026-08-22 04:40 UTCGHSA enrichment
- 2026-08-22 00:37 UTCEG score recompute
- 2026-08-22 00:37 UTCVendor advisory
- 2026-08-22 00:37 UTCGHSA enrichment
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 20:34 UTCGHSA enrichment
- 2026-08-21 16:31 UTCGHSA enrichment
- 2026-08-21 12:27 UTCVendor advisory
- 2026-08-21 12:27 UTCGHSA enrichment
- 2026-08-21 08:24 UTCVendor advisory
- 2026-08-21 08:24 UTCGHSA enrichment
- 2026-08-21 04:21 UTCVendor advisory
- 2026-08-21 04:21 UTCGHSA enrichment
- 2026-08-21 00:18 UTCEG score recompute
- 2026-08-21 00:18 UTCVendor advisory
Frequently asked(5)
What is CVE-2026-17924?
When was CVE-2026-17924 disclosed?
Is CVE-2026-17924 actively exploited?
What is the CVSS score of CVE-2026-17924?
How do I remediate CVE-2026-17924?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-17924
Is Your Infrastructure Affected by CVE-2026-17924?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.