CVE-2026-17916

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 4 sources updated this week
7.5EG
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.2%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Insufficient policy enforcement in Settings in Google Chrome prior to 151.0.7922.72 allowed a remote attacker who had compromised the renderer process to perform privilege escalation via a crafted HTML page. (Chromium security severity: Low)

CVSS v3
7.5
Vendor severity
LOWper Google (Chromium)Vendor's own band, not a CVSS rating — advisory text: (Chromium security severity: Low)
EG Score
7.5HIGHmedium confidence
EG Risk
34
EG Risk 34/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)
Severity75% × 45%
The EG Score, 7.5 of 10.
Exploitation0% × 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.2%
EPSS %ILE
11th
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.

Vendor Advisories for CVE-2026-17916(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 19× in last 7d / 100× 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 321 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 221 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-17916?
CVE-2026-17916 is a high-severity vulnerability; its CVE record was published on July 30, 2026. Insufficient policy enforcement in Settings in Google Chrome prior to 151.0.7922.72 allowed a remote attacker who had compromised the renderer process to perform privilege escalation via a crafted HTML page. (Chromium security severity: Low)
When was the CVE record for CVE-2026-17916 published?
The CVE record for CVE-2026-17916 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-17916 actively exploited?
CVE-2026-17916 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (11th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-17916?
CVE-2026-17916 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-17916?
A fix for CVE-2026-17916 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-17916 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-17916

Explore →

Is Your Infrastructure Affected by CVE-2026-17916?

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