CVE-2026-17993

HIGHPre-NVD 7.07.0
EchelonGraph scoreMEDIUM confidence

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

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

Triggered by: GitHub Security Advisory CVSS
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS, GitHub Security Advisory
7.0EG
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.1%CVSS: 7.0Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Race in Updater in Google Chrome on Windows prior to 151.0.7922.72 allowed a local attacker to perform privilege escalation via a malicious file. (Chromium security severity: Low)

CVSS v3
7.0
Vendor severity
LOWper Google (Chromium)Vendor's own band, not a CVSS rating — advisory text: (Chromium security severity: Low)
EG Score
7.0HIGHmedium confidence
EG Risk
32
EG Risk 32/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)
Severity70% × 45%
The EG Score, 7.0 of 10.
Exploitation<0.1% × 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.1%
EPSS %ILE
below the 1st
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

July 31, 2026

Advisory Details (2)

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

Chromium

https://issues.chromium.org/issues/520532191
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-17993(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 / 76× 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 259 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 159 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.1% · below the 1st percentile
  2. 2026-10-12 16:33 UTCEPSS rescoreEPSS <0.1% · below the 1st 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.1% · below the 1st percentile
  8. 2026-10-10 19:59 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  9. 2026-10-09 20:06 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  10. 2026-10-08 17:11 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  11. 2026-10-07 23:47 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  12. 2026-10-06 23:55 UTCEG score recompute
  13. 2026-10-06 23:55 UTCVendor advisory
  14. 2026-10-06 23:55 UTCGHSA enrichmentGHSA-8854-j33c-jpcf · GitHub severity HIGH · GitHub CVSS 7.0
  15. 2026-10-06 15:17 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  16. 2026-10-05 20:36 UTCVendor advisory
  17. 2026-10-05 20:36 UTCGHSA enrichmentGHSA-8854-j33c-jpcf · GitHub severity HIGH · GitHub CVSS 7.0
  18. 2026-10-05 00:00 UTCVendor advisory
  19. 2026-10-05 00:00 UTCGHSA enrichmentGHSA-8854-j33c-jpcf · GitHub severity HIGH · GitHub CVSS 7.0
  20. 2026-10-04 06:46 UTCEG score recompute
  21. 2026-10-04 06:46 UTCVendor advisory
  22. 2026-10-04 06:46 UTCGHSA enrichmentGHSA-8854-j33c-jpcf · GitHub severity HIGH · GitHub CVSS 7.0
  23. 2026-10-03 14:25 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  24. 2026-10-02 17:09 UTCVendor advisory
  25. 2026-10-02 17:09 UTCGHSA enrichmentGHSA-8854-j33c-jpcf · GitHub severity HIGH · GitHub CVSS 7.0
Show 75 more
  1. 2026-10-01 15:42 UTCVendor advisory
  2. 2026-10-01 15:42 UTCGHSA enrichmentGHSA-8854-j33c-jpcf · GitHub severity HIGH · GitHub CVSS 7.0
  3. 2026-10-01 03:22 UTCEG score recompute
  4. 2026-10-01 03:22 UTCVendor advisory
  5. 2026-10-01 03:22 UTCGHSA enrichmentGHSA-8854-j33c-jpcf · GitHub severity HIGH · GitHub CVSS 7.0
  6. 2026-09-30 15:02 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  7. 2026-09-29 15:20 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  8. 2026-09-29 07:00 UTCEG score recompute
  9. 2026-09-29 07:00 UTCVendor advisory
  10. 2026-09-29 07:00 UTCGHSA enrichmentGHSA-8854-j33c-jpcf · GitHub severity HIGH · GitHub CVSS 7.0
  11. 2026-09-28 13:51 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  12. 2026-09-28 07:11 UTCVendor advisory
  13. 2026-09-28 07:11 UTCGHSA enrichmentGHSA-8854-j33c-jpcf · GitHub severity HIGH · GitHub CVSS 7.0
  14. 2026-09-27 19:07 UTCEG score recompute
  15. 2026-09-27 19:07 UTCVendor advisory
  16. 2026-09-27 19:07 UTCGHSA enrichmentGHSA-8854-j33c-jpcf · GitHub severity HIGH · GitHub CVSS 7.0
  17. 2026-09-27 13:47 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  18. 2026-09-26 15:58 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  19. 2026-09-25 05:00 UTCEG score recompute
  20. 2026-09-25 05:00 UTCVendor advisory
  21. 2026-09-25 05:00 UTCGHSA enrichmentGHSA-8854-j33c-jpcf · GitHub severity HIGH · GitHub CVSS 7.0
  22. 2026-09-24 09:40 UTCVendor advisory
  23. 2026-09-24 09:40 UTCGHSA enrichmentGHSA-8854-j33c-jpcf · GitHub severity HIGH · GitHub CVSS 7.0
  24. 2026-09-23 21:35 UTCEG score recompute
  25. 2026-09-23 21:35 UTCVendor advisory
  26. 2026-09-23 21:35 UTCGHSA enrichmentGHSA-8854-j33c-jpcf · GitHub severity HIGH · GitHub CVSS 7.0
  27. 2026-09-23 03:29 UTCVendor advisory
  28. 2026-09-23 03:29 UTCGHSA enrichmentGHSA-8854-j33c-jpcf · GitHub severity HIGH · GitHub CVSS 7.0
  29. 2026-09-22 15:25 UTCVendor advisory
  30. 2026-09-22 15:25 UTCGHSA enrichmentGHSA-8854-j33c-jpcf · GitHub severity HIGH · GitHub CVSS 7.0
  31. 2026-09-20 21:37 UTCVendor advisory
  32. 2026-09-20 21:37 UTCGHSA enrichmentGHSA-8854-j33c-jpcf · GitHub severity HIGH · GitHub CVSS 7.0
  33. 2026-09-19 23:51 UTCEG score recompute
  34. 2026-09-19 23:51 UTCVendor advisory
  35. 2026-09-19 23:51 UTCGHSA enrichmentGHSA-8854-j33c-jpcf · GitHub severity HIGH · GitHub CVSS 7.0
  36. 2026-09-19 04:24 UTCVendor advisory
  37. 2026-09-19 04:24 UTCGHSA enrichmentGHSA-8854-j33c-jpcf · GitHub severity HIGH · GitHub CVSS 7.0
  38. 2026-09-18 14:55 UTCVendor advisory
  39. 2026-09-18 14:55 UTCGHSA enrichmentGHSA-8854-j33c-jpcf · GitHub severity HIGH · GitHub CVSS 7.0
  40. 2026-09-18 01:26 UTCEG score recompute
  41. 2026-09-18 01:26 UTCVendor advisory
  42. 2026-09-18 01:26 UTCGHSA enrichmentGHSA-8854-j33c-jpcf · GitHub severity HIGH · GitHub CVSS 7.0
  43. 2026-09-17 01:30 UTCEG score recompute
  44. 2026-09-17 01:30 UTCVendor advisory
  45. 2026-09-17 01:30 UTCGHSA enrichmentGHSA-8854-j33c-jpcf · GitHub severity HIGH · GitHub CVSS 7.0
  46. 2026-09-16 14:07 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  47. 2026-09-16 05:40 UTCVendor advisory
  48. 2026-09-16 05:40 UTCGHSA enrichmentGHSA-8854-j33c-jpcf · GitHub severity HIGH · GitHub CVSS 7.0
  49. 2026-09-15 03:27 UTCEG score recompute
  50. 2026-09-15 03:27 UTCVendor advisory
  51. 2026-09-15 03:27 UTCGHSA enrichmentGHSA-8854-j33c-jpcf · GitHub severity HIGH · GitHub CVSS 7.0
  52. 2026-09-14 07:51 UTCVendor advisory
  53. 2026-09-14 07:51 UTCGHSA enrichmentGHSA-8854-j33c-jpcf · GitHub severity HIGH · GitHub CVSS 7.0
  54. 2026-09-13 19:47 UTCVendor advisory
  55. 2026-09-13 19:47 UTCGHSA enrichmentGHSA-8854-j33c-jpcf · GitHub severity HIGH · GitHub CVSS 7.0
  56. 2026-09-13 07:33 UTCVendor advisory
  57. 2026-09-13 07:33 UTCGHSA enrichmentGHSA-8854-j33c-jpcf · GitHub severity HIGH · GitHub CVSS 7.0
  58. 2026-09-12 19:29 UTCEG score recompute
  59. 2026-09-12 19:29 UTCVendor advisory
  60. 2026-09-12 19:29 UTCGHSA enrichmentGHSA-8854-j33c-jpcf · GitHub severity HIGH · GitHub CVSS 7.0
  61. 2026-09-12 15:00 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  62. 2026-09-12 07:25 UTCVendor advisory
  63. 2026-09-12 07:25 UTCGHSA enrichmentGHSA-8854-j33c-jpcf · GitHub severity HIGH · GitHub CVSS 7.0
  64. 2026-09-11 19:21 UTCEG score recompute
  65. 2026-09-11 19:21 UTCVendor advisory
  66. 2026-09-11 19:21 UTCGHSA enrichmentGHSA-8854-j33c-jpcf · GitHub severity HIGH · GitHub CVSS 7.0
  67. 2026-09-11 14:52 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  68. 2026-09-11 09:36 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  69. 2026-09-11 07:16 UTCGHSA enrichmentGHSA-8854-j33c-jpcf · GitHub severity HIGH · GitHub CVSS 7.0
  70. 2026-09-10 19:12 UTCEG score recompute
  71. 2026-09-10 19:12 UTCGHSA enrichmentGHSA-8854-j33c-jpcf · GitHub severity HIGH · GitHub CVSS 7.0
  72. 2026-09-10 09:34 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  73. 2026-09-10 03:57 UTCGHSA enrichmentGHSA-8854-j33c-jpcf · GitHub severity HIGH · GitHub CVSS 7.0
  74. 2026-09-09 07:25 UTCEG score recompute
  75. 2026-09-09 07:25 UTCGHSA enrichmentGHSA-8854-j33c-jpcf · GitHub severity HIGH · GitHub CVSS 7.0

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-17993?
CVE-2026-17993 is a high-severity vulnerability; its CVE record was published on July 30, 2026. Race in Updater in Google Chrome on Windows prior to 151.0.7922.72 allowed a local attacker to perform privilege escalation via a malicious file. (Chromium security severity: Low)
When was the CVE record for CVE-2026-17993 published?
The CVE record for CVE-2026-17993 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 July 31, 2026; the record at its source may have been updated since.
Is CVE-2026-17993 actively exploited?
CVE-2026-17993 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a <0.1% probability of exploitation in the next 30 days (below the 1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-17993?
CVE-2026-17993 has a CVSS v3.1 base score of 7.0 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-17993?
A fix for CVE-2026-17993 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-17993 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-17993

Explore →

Is Your Infrastructure Affected by CVE-2026-17993?

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

Book a Demo →Browse All CVEs