CVE-2026-17711

CRITICALPre-NVD 9.69.6
EchelonGraph scoreMEDIUM confidence

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

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.

Triggered by: GitHub Security Advisory CVSS
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS, GitHub Security Advisory
Trending — 4 sources updated this week
9.6EG
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: 9.6Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Race in Downloads in Google Chrome on Mac 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)

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.6CRITICALmedium confidence
EG Risk
43
EG Risk 43/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)
Severity96% × 45%
The EG Score, 9.6 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
18th
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 Oct 7, 2026
Patch available.
Web page

Chromium

https://issues.chromium.org/issues/519996040
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-17711(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 18× in last 7d / 139× 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 605 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 505 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-17711?
CVE-2026-17711 is a critical-severity vulnerability; its CVE record was published on July 30, 2026. Race in Downloads in Google Chrome on Mac 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)
When was the CVE record for CVE-2026-17711 published?
The CVE record for CVE-2026-17711 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-17711 actively exploited?
CVE-2026-17711 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (18th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-17711?
CVE-2026-17711 has a CVSS v3.1 base score of 9.6 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-17711?
A fix for CVE-2026-17711 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-17711 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-17711

Explore →

Is Your Infrastructure Affected by CVE-2026-17711?

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

Book a Demo →Browse All CVEs