CVE-2026-17702

LOWPre-NVD 3.13.1
EchelonGraph scoreMEDIUM confidence

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

Score 3.1 from GitHub Security Advisory (severity: LOW) published 2026-07-30. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 3.1; 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
3.1EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 3.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Inappropriate implementation in Skia in Google Chrome prior to 151.0.7922.72 allowed a remote attacker who had compromised the renderer process to leak cross-origin data via a crafted HTML page. (Chromium security severity: High)

CVSS v3
3.1
Vendor severity
HIGHper Google (Chromium)Vendor's own band, not a CVSS rating — advisory text: (Chromium security severity: High)
EG Score
3.1LOWmedium confidence
EG Risk
14
EG Risk 14/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)
Severity31% × 45%
The EG Score, 3.1 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 every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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
21st
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 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 partial (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

References (2)

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatwebkit2gtk3-0:2.54.0-1.el8_102026-09-30redhat
redhatwebkit2gtk3-0:2.54.0-1.el9_82026-09-21redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(11 across 4 ecosystems)
Debian:14(4)
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
—
libskia146.20260311+dfsg-1 ... 146.20260602~git.3476902+dfsg-3 (12 versions)
  • every version up to 146.20260602~git.3476902+dfsg-4: fixed in 146.20260602~git.3476902+dfsg-4
—
webkit2gtk2.48.3-1 ... 2.54.0-1~exp1 (61 versions)
  • every version on: no fix on record
—
wpewebkit2.48.3-1 ... 2.52.6-1 (20 versions)
  • every version up to 2.54.0-1: fixed in 2.54.0-1
—
Debian:12(3)
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
—
webkit2gtk2.40.1-1 ... 2.54.0-1~exp1 (168 versions)
  • every version on: no fix on record
—
wpewebkit2.38.6-1 ... 2.54.0-2 (56 versions)
  • every version on: no fix on record
—
Debian:13(3)
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
—
webkit2gtk2.48.3-1 ... 2.53.92-1 (59 versions)
  • every version up to 2.54.0-1~deb13u1: fixed in 2.54.0-1~deb13u1
—
wpewebkit2.48.3-1 ... 2.54.0-2 (22 versions)
  • every version on: no fix on record
—
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
—

Weakness Classification(1)

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

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-17702?
CVE-2026-17702 is a low-severity vulnerability; its CVE record was published on July 30, 2026. Inappropriate implementation in Skia in Google Chrome prior to 151.0.7922.72 allowed a remote attacker who had compromised the renderer process to leak cross-origin data via a crafted HTML page. (Chromium security severity: High)
When was the CVE record for CVE-2026-17702 published?
The CVE record for CVE-2026-17702 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-17702 actively exploited?
CVE-2026-17702 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (21st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-17702?
CVE-2026-17702 has a CVSS v3.1 base score of 3.1 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-17702?
A fix for CVE-2026-17702 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-17702 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-17702

Explore →

Is Your Infrastructure Affected by CVE-2026-17702?

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