CVE-2026-17868

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-30. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS, GitHub Security Advisory
8.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 8.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Insufficient policy enforcement in USB in Google Chrome prior to 151.0.7922.72 allowed a remote attacker to perform privilege escalation via a crafted HTML page. (Chromium security severity: Medium)

CVSS v3
8.8
Vendor severity
MEDIUMper Google (Chromium)Vendor's own band, not a CVSS rating — advisory text: (Chromium security severity: Medium)
EG Score
8.8HIGHmedium confidence
EG Risk
40
EG Risk 40/100

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 computed (value × EchelonGraph’s weight)
Severity88% × 45%
The EG Score, 8.8 of 10.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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.
EPSS PROB
0.3%
EPSS %ILE
24th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (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

Published

July 30, 2026

Last Modified

August 3, 2026

Advisory Details (2)

Auto-updated Jul 30, 2026
Patch available.
Web page

Chromium

https://issues.chromium.org/issues/520743499
Web page

Chrome Releases: Stable Channel Update for Desktop

https://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_0887107924.html

Vendor Advisories for CVE-2026-17868(2)

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)
PackageVulnerable rangeFix by version rangeDependents
chromium100.0.4896.127-1 ... 99.0.4844.84-1~deb11u1 (500 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
chromium113.0.5672.126-1 ... 151.0.7922.47-1 (394 versions)
  • every version up to 151.0.7922.71-1~deb12u1: fixed in 151.0.7922.71-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
chromium138.0.7204.183-1 ... 151.0.7922.71-1~deb12u1 (160 versions)
  • every version up to 151.0.7922.71-1~deb13u1: fixed in 151.0.7922.71-1~deb13u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
chromium138.0.7204.183-1 ... 151.0.7922.71-1~deb13u1 (161 versions)
  • every version up to 151.0.7922.71-1: fixed in 151.0.7922.71-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 86× 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 303 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 203 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  2. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  3. 2026-10-12 16:28 UTCEG score recompute
  4. 2026-10-11 20:08 UTCEG score recompute
  5. 2026-10-11 17:20 UTCEG score recompute
  6. 2026-10-11 14:53 UTCEG score recompute
  7. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  8. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  9. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  10. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  11. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  12. 2026-10-06 23:57 UTCEG score recompute
  13. 2026-10-06 23:57 UTCVendor advisory
  14. 2026-10-06 23:57 UTCGHSA enrichmentGHSA-m5f9-xcc3-c2pj · GitHub severity HIGH · GitHub CVSS 8.8
  15. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  16. 2026-10-05 20:42 UTCEG score recompute
  17. 2026-10-05 20:42 UTCVendor advisory
  18. 2026-10-05 20:42 UTCGHSA enrichmentGHSA-m5f9-xcc3-c2pj · GitHub severity HIGH · GitHub CVSS 8.8
  19. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  20. 2026-10-05 00:01 UTCEG score recompute
  21. 2026-10-05 00:01 UTCVendor advisory
  22. 2026-10-05 00:01 UTCGHSA enrichmentGHSA-m5f9-xcc3-c2pj · GitHub severity HIGH · GitHub CVSS 8.8
  23. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  24. 2026-10-04 06:50 UTCEG score recompute
  25. 2026-10-04 06:50 UTCVendor advisory
Show 75 more
  1. 2026-10-04 06:50 UTCGHSA enrichmentGHSA-m5f9-xcc3-c2pj · GitHub severity HIGH · GitHub CVSS 8.8
  2. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  3. 2026-10-02 17:35 UTCEG score recompute
  4. 2026-10-02 17:35 UTCVendor advisory
  5. 2026-10-02 17:35 UTCGHSA enrichmentGHSA-m5f9-xcc3-c2pj · GitHub severity HIGH · GitHub CVSS 8.8
  6. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  7. 2026-10-01 03:27 UTCEG score recompute
  8. 2026-10-01 03:27 UTCVendor advisory
  9. 2026-10-01 03:27 UTCGHSA enrichmentGHSA-m5f9-xcc3-c2pj · GitHub severity HIGH · GitHub CVSS 8.8
  10. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  11. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  12. 2026-09-29 07:22 UTCEG score recompute
  13. 2026-09-29 07:22 UTCVendor advisory
  14. 2026-09-29 07:22 UTCGHSA enrichmentGHSA-m5f9-xcc3-c2pj · GitHub severity HIGH · GitHub CVSS 8.8
  15. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  16. 2026-09-28 08:21 UTCVendor advisory
  17. 2026-09-28 08:20 UTCGHSA enrichmentGHSA-m5f9-xcc3-c2pj · GitHub severity HIGH · GitHub CVSS 8.8
  18. 2026-09-27 19:09 UTCEG score recompute
  19. 2026-09-27 19:09 UTCVendor advisory
  20. 2026-09-27 19:09 UTCGHSA enrichmentGHSA-m5f9-xcc3-c2pj · GitHub severity HIGH · GitHub CVSS 8.8
  21. 2026-09-27 13:47 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  22. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  23. 2026-09-25 05:02 UTCEG score recompute
  24. 2026-09-25 05:02 UTCVendor advisory
  25. 2026-09-25 05:02 UTCGHSA enrichmentGHSA-m5f9-xcc3-c2pj · GitHub severity HIGH · GitHub CVSS 8.8
  26. 2026-09-24 10:56 UTCVendor advisory
  27. 2026-09-24 10:56 UTCGHSA enrichmentGHSA-m5f9-xcc3-c2pj · GitHub severity HIGH · GitHub CVSS 8.8
  28. 2026-09-23 21:40 UTCEG score recompute
  29. 2026-09-23 21:40 UTCVendor advisory
  30. 2026-09-23 21:40 UTCGHSA enrichmentGHSA-m5f9-xcc3-c2pj · GitHub severity HIGH · GitHub CVSS 8.8
  31. 2026-09-23 04:48 UTCVendor advisory
  32. 2026-09-23 04:48 UTCGHSA enrichmentGHSA-m5f9-xcc3-c2pj · GitHub severity HIGH · GitHub CVSS 8.8
  33. 2026-09-22 15:32 UTCEG score recompute
  34. 2026-09-22 15:32 UTCVendor advisory
  35. 2026-09-22 15:32 UTCGHSA enrichmentGHSA-m5f9-xcc3-c2pj · GitHub severity HIGH · GitHub CVSS 8.8
  36. 2026-09-20 21:37 UTCEG score recompute
  37. 2026-09-20 21:37 UTCVendor advisory
  38. 2026-09-20 21:37 UTCGHSA enrichmentGHSA-m5f9-xcc3-c2pj · GitHub severity HIGH · GitHub CVSS 8.8
  39. 2026-09-19 23:59 UTCEG score recompute
  40. 2026-09-19 23:59 UTCVendor advisory
  41. 2026-09-19 23:59 UTCGHSA enrichmentGHSA-m5f9-xcc3-c2pj · GitHub severity HIGH · GitHub CVSS 8.8
  42. 2026-09-19 04:27 UTCEG score recompute
  43. 2026-09-19 04:27 UTCVendor advisory
  44. 2026-09-19 04:27 UTCGHSA enrichmentGHSA-m5f9-xcc3-c2pj · GitHub severity HIGH · GitHub CVSS 8.8
  45. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  46. 2026-09-18 14:56 UTCVendor advisory
  47. 2026-09-18 14:56 UTCGHSA enrichmentGHSA-m5f9-xcc3-c2pj · GitHub severity HIGH · GitHub CVSS 8.8
  48. 2026-09-18 01:35 UTCEG score recompute
  49. 2026-09-18 01:35 UTCVendor advisory
  50. 2026-09-18 01:35 UTCGHSA enrichmentGHSA-m5f9-xcc3-c2pj · GitHub severity HIGH · GitHub CVSS 8.8
  51. 2026-09-17 01:32 UTCEG score recompute
  52. 2026-09-17 01:32 UTCVendor advisory
  53. 2026-09-17 01:32 UTCGHSA enrichmentGHSA-m5f9-xcc3-c2pj · GitHub severity HIGH · GitHub CVSS 8.8
  54. 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  55. 2026-09-16 05:43 UTCEG score recompute
  56. 2026-09-16 05:43 UTCVendor advisory
  57. 2026-09-16 05:43 UTCGHSA enrichmentGHSA-m5f9-xcc3-c2pj · GitHub severity HIGH · GitHub CVSS 8.8
  58. 2026-09-16 05:14 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  59. 2026-09-15 03:48 UTCEG score recompute
  60. 2026-09-15 03:48 UTCVendor advisory
  61. 2026-09-15 03:48 UTCGHSA enrichmentGHSA-m5f9-xcc3-c2pj · GitHub severity HIGH · GitHub CVSS 8.8
  62. 2026-09-14 04:27 UTCEG score recompute
  63. 2026-09-14 04:27 UTCVendor advisory
  64. 2026-09-14 04:27 UTCGHSA enrichmentGHSA-m5f9-xcc3-c2pj · GitHub severity HIGH · GitHub CVSS 8.8
  65. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  66. 2026-09-13 15:18 UTCVendor advisory
  67. 2026-09-13 15:18 UTCGHSA enrichmentGHSA-m5f9-xcc3-c2pj · GitHub severity HIGH · GitHub CVSS 8.8
  68. 2026-09-13 01:37 UTCEG score recompute
  69. 2026-09-13 01:37 UTCVendor advisory
  70. 2026-09-13 01:37 UTCGHSA enrichmentGHSA-m5f9-xcc3-c2pj · GitHub severity HIGH · GitHub CVSS 8.8
  71. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  72. 2026-09-12 12:28 UTCVendor advisory
  73. 2026-09-12 12:28 UTCGHSA enrichmentGHSA-m5f9-xcc3-c2pj · GitHub severity HIGH · GitHub CVSS 8.8
  74. 2026-09-11 21:33 UTCEG score recompute
  75. 2026-09-11 21:33 UTCVendor advisory

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-17868?
CVE-2026-17868 is a high-severity vulnerability; its CVE record was published on July 30, 2026. Insufficient policy enforcement in USB in Google Chrome prior to 151.0.7922.72 allowed a remote attacker to perform privilege escalation via a crafted HTML page. (Chromium security severity: Medium)
When was the CVE record for CVE-2026-17868 published?
The CVE record for CVE-2026-17868 was published on July 30, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 3, 2026; the record at its source may have been updated since.
Is CVE-2026-17868 actively exploited?
CVE-2026-17868 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (24th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-17868?
CVE-2026-17868 has a CVSS v3.1 base score of 8.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-17868?
A fix for CVE-2026-17868 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-17868 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-17868

Explore →

Is Your Infrastructure Affected by CVE-2026-17868?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs