CVE-2026-17687

CRITICALPre-NVD 9.69.6—
EchelonGraph scoreHIGH confidence

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, epss, ghsa
Trending — 4 sources updated this week
9.6EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.6Exploit: None knownExposed: 0

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

Type Confusion in ANGLE in Google Chrome 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.6(high)
EG Risk
43(Track)
EG Risk 43/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
Severity96% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
43%
KEV
Not listed

Published

July 30, 2026

Last Modified

August 3, 2026

Advisory Details (2)

Auto-updated Aug 23, 2026
No patch confirmed yet.
generic

Chromium

https://issues.chromium.org/issues/516985726
generic

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-17687(1)

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 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 ... 151.0.7922.47-1 (394 versions)151.0.7922.71-1~deb12u1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
chromium138.0.7204.183-1 ... 151.0.7922.71-1~deb12u1 (160 versions)151.0.7922.71-1~deb13u1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
chromium138.0.7204.183-1 ... 151.0.7922.71-1~deb13u1 (162 versions)——

Weakness Classification(1)

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

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 89× in last 7d / 332× 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 332 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-17687?
CVE-2026-17687 is a critical vulnerability published on July 30, 2026. Type Confusion in ANGLE in Google Chrome 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 CVE-2026-17687 disclosed?
CVE-2026-17687 was first published in the National Vulnerability Database on July 30, 2026, with the most recent update on August 3, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-17687 actively exploited?
CVE-2026-17687 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 57.3% of all scored CVEs.
What is the CVSS score of CVE-2026-17687?
CVE-2026-17687 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-17687?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-17687, 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-17687

Explore →

Is Your Infrastructure Affected by CVE-2026-17687?

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

Start Free Scan →Browse All CVEs