CVE-2026-17670

CRITICALPre-NVD 9.69.6—
EchelonGraph scoreMEDIUM 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: 0%CVSS: 9.6Exploit: None knownExposed: 0

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

Use after free in Views 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(medium)
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%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
39%
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/513228974
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-17670(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 73× in last 7d / 369× 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 379 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-17670?
CVE-2026-17670 is a critical vulnerability published on July 30, 2026. Use after free in Views 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-17670 disclosed?
CVE-2026-17670 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-17670 actively exploited?
CVE-2026-17670 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 60.7% of all scored CVEs.
What is the CVSS score of CVE-2026-17670?
CVE-2026-17670 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-17670?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-17670, 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-17670

Explore →

Is Your Infrastructure Affected by CVE-2026-17670?

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

Start Free Scan →Browse All CVEs