CVE-2026-16417

LOWPre-NVD 3.13.1—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 4 sources updated this week
3.1EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 3.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Uninitialized Use in Skia in Google Chrome prior to 150.0.7871.182 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.1(medium)
EG Risk
14(Track)
EG Risk 14/100SSVC: Track

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
Severity31% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
13%
KEV
Not listed

Published

July 21, 2026

Last Modified

July 24, 2026

References (2)

Vendor Advisories for CVE-2026-16417(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(5 across 4 ecosystems)
Debian:14(2)
PackageVulnerable rangeFixed inDependents
chromium138.0.7204.183-1 ... 150.0.7871.46-1~deb13u1 (157 versions)150.0.7871.181-1—
libskia146.20260311+dfsg-1 ... 146.20260602~git.3476902+dfsg-3 (12 versions)——
Debian:11(1)
PackageVulnerable rangeFixed inDependents
chromium100.0.4896.127-1 ... 99.0.4844.84-1~deb11u1 (500 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
chromium113.0.5672.126-1 ... 150.0.7871.46-1~deb13u1 (390 versions)150.0.7871.181-1~deb12u1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
chromium138.0.7204.183-1 ... 150.0.7871.46-1~deb13u1 (156 versions)150.0.7871.181-1~deb13u1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 49× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 384 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-16417?
CVE-2026-16417 is a low vulnerability published on July 21, 2026. Uninitialized Use in Skia in Google Chrome prior to 150.0.7871.182 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 CVE-2026-16417 disclosed?
CVE-2026-16417 was first published in the National Vulnerability Database on July 21, 2026, with the most recent update on July 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-16417 actively exploited?
CVE-2026-16417 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 87.1% of all scored CVEs.
What is the CVSS score of CVE-2026-16417?
CVE-2026-16417 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-16417?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-16417, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-16417?

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

Start Free Scan →Browse All CVEs