CVE-2026-11170

HIGHPre-NVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
8.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.1Exploit: NoneExposed: 0

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

Inappropriate implementation in Chromoting in Google Chrome on Linux prior to 149.0.7827.53 allowed a remote attacker to perform OS-level privilege escalation via malicious network traffic. (Chromium security severity: Medium)

CVSS v3
8.1
EG Score
8.1(medium)
EG Risk
37(Track)
EG Risk 37/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
Severity81% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
15.0%
KEV
Not listed

Published

June 4, 2026

Last Modified

July 23, 2026

Advisory Details (2)

Auto-updated Jun 5, 2026
No patch confirmed yet.
generic

Chromium

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

Chrome Releases: Stable Channel Update for Desktop

https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop.html

Vendor Advisories for CVE-2026-11170(2)

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

Weakness Classification(1)

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

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-11170?
CVE-2026-11170 is a high vulnerability published on June 4, 2026. Inappropriate implementation in Chromoting in Google Chrome on Linux prior to 149.0.7827.53 allowed a remote attacker to perform OS-level privilege escalation via malicious network traffic. (Chromium security severity: Medium)
When was CVE-2026-11170 disclosed?
CVE-2026-11170 was first published in the National Vulnerability Database on June 4, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-11170 actively exploited?
CVE-2026-11170 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 15.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-11170?
CVE-2026-11170 has a CVSS v3.1 base score of 8.1 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-11170?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-11170, 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

Explore the affected products and dependency analysis for CVE-2026-11170

Explore →

Is Your Infrastructure Affected by CVE-2026-11170?

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

Start Free Scan →Browse All CVEs