Policy bypass in Enterprise in Google Chrome prior to 151.0.7922.72 allowed a remote attacker to bypass navigation restrictions via a crafted domain name. (Chromium security severity: Low)
CVE-2026-17923
Score 6.5 from GitHub Security Advisory published 2026-07-30. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 6.5; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.5
- Vendor severity
- LOWper Google (Chromium)Vendor's own band, not a CVSS rating — advisory text: (Chromium security severity: Low)
- EG Score
- 6.5(high)
- EG Risk
- 29(Track)EG Risk 29/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 computedSeverity65% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 11%
- KEV
- Not listed
Published
July 30, 2026
Last Modified
August 3, 2026
Advisory Details (2)
Auto-updated Jul 30, 2026Chrome Releases: Stable Channel Update for Desktop
https://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_0887107924.htmlVendor Advisories for CVE-2026-17923(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 22× in last 7d / 99× 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-25 13:48 UTCEPSS rescore
- 2026-08-25 09:45 UTCEG score recompute
- 2026-08-25 09:45 UTCVendor advisory
- 2026-08-25 09:45 UTCGHSA enrichment
- 2026-08-24 07:45 UTCVendor advisory
- 2026-08-24 07:45 UTCGHSA enrichment
- 2026-08-23 05:46 UTCEG score recompute
- 2026-08-23 05:46 UTCVendor advisory
- 2026-08-23 05:46 UTCGHSA enrichment
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 03:48 UTCEG score recompute
- 2026-08-22 03:48 UTCVendor advisory
- 2026-08-22 03:48 UTCGHSA enrichment
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 01:49 UTCEG score recompute
- 2026-08-21 01:49 UTCVendor advisory
- 2026-08-21 01:49 UTCGHSA enrichment
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-19 23:49 UTCEG score recompute
- 2026-08-19 23:49 UTCVendor advisory
- 2026-08-19 23:49 UTCGHSA enrichment
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-18 21:50 UTCEG score recompute
- 2026-08-18 21:50 UTCVendor advisory
- 2026-08-18 21:50 UTCGHSA enrichment
Show 74 moreShow fewer
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 19:51 UTCEG score recompute
- 2026-08-17 19:51 UTCVendor advisory
- 2026-08-17 19:51 UTCGHSA enrichment
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-16 17:26 UTCEG score recompute
- 2026-08-16 17:26 UTCVendor advisory
- 2026-08-16 17:26 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 15:28 UTCEG score recompute
- 2026-08-15 15:28 UTCVendor advisory
- 2026-08-15 15:28 UTCGHSA enrichment
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 13:29 UTCEG score recompute
- 2026-08-14 13:29 UTCVendor advisory
- 2026-08-14 13:29 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 11:31 UTCEG score recompute
- 2026-08-13 11:31 UTCVendor advisory
- 2026-08-13 11:31 UTCGHSA enrichment
- 2026-08-12 13:50 UTCEPSS rescore
- 2026-08-12 09:33 UTCEG score recompute
- 2026-08-12 09:33 UTCVendor advisory
- 2026-08-12 09:33 UTCGHSA enrichment
- 2026-08-11 13:42 UTCEPSS rescore
- 2026-08-11 07:34 UTCEG score recompute
- 2026-08-11 07:34 UTCVendor advisory
- 2026-08-11 07:34 UTCGHSA enrichment
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 05:36 UTCEG score recompute
- 2026-08-10 05:36 UTCVendor advisory
- 2026-08-10 05:36 UTCGHSA enrichment
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 03:38 UTCEG score recompute
- 2026-08-09 03:38 UTCVendor advisory
- 2026-08-09 03:38 UTCGHSA enrichment
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 01:40 UTCEG score recompute
- 2026-08-08 01:40 UTCVendor advisory
- 2026-08-08 01:40 UTCGHSA enrichment
- 2026-08-06 23:41 UTCEG score recompute
- 2026-08-06 23:41 UTCVendor advisory
- 2026-08-06 23:41 UTCGHSA enrichment
- 2026-08-06 13:46 UTCEPSS rescore
- 2026-08-05 21:43 UTCEG score recompute
- 2026-08-05 21:43 UTCVendor advisory
- 2026-08-05 21:43 UTCGHSA enrichment
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-04 19:45 UTCEG score recompute
- 2026-08-04 19:45 UTCVendor advisory
- 2026-08-04 19:45 UTCGHSA enrichment
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-04 10:38 UTCEPSS rescore
- 2026-08-03 17:47 UTCEG score recompute
- 2026-08-03 17:46 UTCGHSA enrichment
- 2026-08-03 10:35 UTCEPSS rescore
- 2026-08-03 02:33 UTCEG score recompute
- 2026-08-03 02:33 UTCVendor advisory
- 2026-08-03 02:33 UTCGHSA enrichment
- 2026-08-02 02:26 UTCEPSS rescore
- 2026-08-02 00:34 UTCEG score recompute
- 2026-08-02 00:34 UTCVendor advisory
- 2026-08-02 00:34 UTCGHSA enrichment
- 2026-08-01 04:15 UTCEPSS rescore
- 2026-07-31 22:36 UTCEG score recompute
- 2026-07-31 22:35 UTCGHSA enrichment
- 2026-07-30 20:35 UTCGHSA enrichment
- 2026-07-30 19:34 UTCEG score recompute▲ 6.50
- 2026-07-30 19:33 UTCGHSA enrichment
- 2026-07-30 19:31 UTCMITRE cvelistV5CVSS v3 → 6.5 · severity → MEDIUM
- 2026-07-30 01:22 UTCNVD update
- 2026-07-30 00:55 UTCEG score recompute
- 2026-07-30 00:52 UTCMITRE cvelistV5first tracked
Related CVEs(same vendor + same CWE)
Same vendor
10 shownmsrc
Same CWE
10 shownCWE-693
- CVE-2021-32835EG 9.9EPSS p91CRITICAL
- CVE-2019-10328EG 9.9CRITICAL
- CVE-2019-1003030EG 9.9 KEVEPSS p100CRITICAL
- CVE-2021-27497NVD 6.5EG 9.8CRITICAL
- CVE-2020-10887EG 9.8EPSS p90CRITICAL
- CVE-2017-3197EG 9.8EPSS p92CRITICAL
- CVE-2018-9318EG 9.8EPSS p90CRITICAL
- CVE-2018-9311EG 9.8EPSS p90CRITICAL
- CVE-2017-8864EG 9.8CRITICAL
- CVE-2013-2465EG 9.8 KEVEPSS p100CRITICAL
Frequently asked(5)
What is CVE-2026-17923?
When was CVE-2026-17923 disclosed?
Is CVE-2026-17923 actively exploited?
What is the CVSS score of CVE-2026-17923?
How do I remediate CVE-2026-17923?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-17923
Is Your Infrastructure Affected by CVE-2026-17923?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.