Integer overflow in QUIC 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: High)
CVE-2026-17673
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
- HIGHper Google (Chromium)Vendor's own band, not a CVSS rating — advisory text: (Chromium security severity: High)
- 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
- 40%
- KEV
- Not listed
Published
July 30, 2026
Last Modified
August 3, 2026
Advisory Details (2)
Auto-updated Sep 14, 2026Chrome Releases: Stable Channel Update for Desktop
https://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_0887107924.htmlVendor Advisories for CVE-2026-17673(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 ... 152.0.7977.64-1 (177 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 56× in last 7d / 246× 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 456 total refreshes for this CVE.
- 2026-09-15 07:23 UTCEG score recompute
- 2026-09-15 07:23 UTCVendor advisory
- 2026-09-15 07:23 UTCGHSA enrichment
- 2026-09-14 15:48 UTCVendor advisory
- 2026-09-14 15:48 UTCGHSA enrichment
- 2026-09-14 11:23 UTCVendor advisory
- 2026-09-14 11:23 UTCGHSA enrichment
- 2026-09-14 06:59 UTCVendor advisory
- 2026-09-14 06:59 UTCGHSA enrichment
- 2026-09-14 02:35 UTCVendor advisory
- 2026-09-14 02:35 UTCGHSA enrichment
- 2026-09-13 22:10 UTCVendor advisory
- 2026-09-13 22:10 UTCGHSA enrichment
- 2026-09-13 17:39 UTCEG score recompute
- 2026-09-13 17:39 UTCVendor advisory
- 2026-09-13 17:39 UTCGHSA enrichment
- 2026-09-13 16:46 UTCEPSS rescore
- 2026-09-13 13:12 UTCVendor advisory
- 2026-09-13 13:12 UTCGHSA enrichment
- 2026-09-13 08:48 UTCVendor advisory
- 2026-09-13 08:48 UTCGHSA enrichment
- 2026-09-13 04:23 UTCVendor advisory
- 2026-09-13 04:23 UTCGHSA enrichment
- 2026-09-12 23:58 UTCVendor advisory
- 2026-09-12 23:58 UTCGHSA enrichment
Show 75 moreShow fewer
- 2026-09-12 18:18 UTCEG score recompute
- 2026-09-12 18:18 UTCVendor advisory
- 2026-09-12 18:18 UTCGHSA enrichment
- 2026-09-12 15:00 UTCEPSS rescore
- 2026-09-12 13:53 UTCVendor advisory
- 2026-09-12 13:53 UTCGHSA enrichment
- 2026-09-12 09:29 UTCVendor advisory
- 2026-09-12 09:29 UTCGHSA enrichment
- 2026-09-12 05:02 UTCVendor advisory
- 2026-09-12 05:02 UTCGHSA enrichment
- 2026-09-12 00:37 UTCVendor advisory
- 2026-09-12 00:37 UTCGHSA enrichment
- 2026-09-11 19:32 UTCVendor advisory
- 2026-09-11 19:32 UTCGHSA enrichment
- 2026-09-11 15:04 UTCEG score recompute
- 2026-09-11 15:04 UTCVendor advisory
- 2026-09-11 15:04 UTCGHSA enrichment
- 2026-09-11 14:52 UTCEPSS rescore
- 2026-09-11 09:36 UTCEPSS rescore
- 2026-09-11 06:26 UTCGHSA enrichment
- 2026-09-11 01:20 UTCGHSA enrichment
- 2026-09-10 19:40 UTCGHSA enrichment
- 2026-09-10 14:34 UTCGHSA enrichment
- 2026-09-10 10:09 UTCEG score recompute
- 2026-09-10 10:09 UTCGHSA enrichment
- 2026-09-10 09:34 UTCEPSS rescore
- 2026-09-10 04:27 UTCGHSA enrichment
- 2026-09-09 12:05 UTCVendor advisory
- 2026-09-09 12:05 UTCGHSA enrichment
- 2026-09-09 07:40 UTCEG score recompute
- 2026-09-09 07:40 UTCGHSA enrichment
- 2026-09-08 22:00 UTCEPSS rescore
- 2026-09-08 00:57 UTCVendor advisory
- 2026-09-08 00:57 UTCGHSA enrichment
- 2026-09-07 20:33 UTCEG score recompute
- 2026-09-07 20:33 UTCVendor advisory
- 2026-09-07 20:32 UTCGHSA enrichment
- 2026-09-07 16:01 UTCEPSS rescore
- 2026-09-06 22:00 UTCVendor advisory
- 2026-09-06 22:00 UTCGHSA enrichment
- 2026-09-06 17:22 UTCEG score recompute
- 2026-09-06 17:22 UTCVendor advisory
- 2026-09-06 17:22 UTCGHSA enrichment
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-06 12:42 UTCVendor advisory
- 2026-09-06 12:42 UTCGHSA enrichment
- 2026-09-06 08:16 UTCVendor advisory
- 2026-09-06 08:16 UTCGHSA enrichment
- 2026-09-06 03:50 UTCVendor advisory
- 2026-09-06 03:50 UTCGHSA enrichment
- 2026-09-05 23:24 UTCVendor advisory
- 2026-09-05 23:24 UTCGHSA enrichment
- 2026-09-05 19:00 UTCEG score recompute
- 2026-09-05 19:00 UTCVendor advisory
- 2026-09-05 19:00 UTCGHSA enrichment
- 2026-09-05 09:30 UTCVendor advisory
- 2026-09-05 09:30 UTCGHSA enrichment
- 2026-09-05 05:05 UTCVendor advisory
- 2026-09-05 05:05 UTCGHSA enrichment
- 2026-09-04 16:16 UTCEG score recompute
- 2026-09-04 16:16 UTCVendor advisory
- 2026-09-04 16:16 UTCGHSA enrichment
- 2026-09-04 11:50 UTCEG score recompute
- 2026-09-04 11:50 UTCVendor advisory
- 2026-09-04 11:50 UTCGHSA enrichment
- 2026-09-04 05:06 UTCEPSS rescore
- 2026-09-02 14:11 UTCEPSS rescore
- 2026-09-01 22:44 UTCEG score recompute
- 2026-09-01 22:44 UTCVendor advisory
- 2026-09-01 22:44 UTCGHSA enrichment
- 2026-09-01 13:53 UTCEPSS rescore
- 2026-09-01 04:39 UTCEPSS rescore
- 2026-08-31 23:50 UTCVendor advisory
- 2026-08-31 23:50 UTCGHSA enrichment
- 2026-08-31 06:41 UTCVendor advisory
Related CVEs(same vendor + same CWE)
Same vendor
10 shownmsrc
Same CWE
10 shownCWE-190
Frequently asked(5)
What is CVE-2026-17673?
When was CVE-2026-17673 disclosed?
Is CVE-2026-17673 actively exploited?
What is the CVSS score of CVE-2026-17673?
How do I remediate CVE-2026-17673?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-17673
Is Your Infrastructure Affected by CVE-2026-17673?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.