CVE-2026-17877

HIGHPre-NVD 8.48.4
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.4 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.1% (2nd percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 7.5 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-07-30) is not newer than that change (2026-08-03), so it does not.

Triggered by: Headline CVSS from CISA-ADP (Vulnrichment) CVSS v3.1
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS, GitHub Security Advisory
8.4EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 8.4Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

CVSS v3
8.4
Vendor severity
MEDIUMper Google (Chromium)Vendor's own band, not a CVSS rating — advisory text: (Chromium security severity: Medium)
EG Score
8.4HIGHmedium confidence
EG Risk
38
EG Risk 38/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)
Severity84% × 45%
The EG Score, 8.4 of 10.
Exploitation0.1% × 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 low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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.1%
EPSS %ILE
2nd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

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

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

Advisory Details (2)

Auto-updated Jul 30, 2026
Patch available.
Web page

Chromium

https://issues.chromium.org/issues/522426086
Web page

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-17877(2)

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 rangeFix by version rangeDependents
chromium100.0.4896.127-1 ... 99.0.4844.84-1~deb11u1 (500 versions)
  • every version on: no fix on record
—
Debian:12(1)
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
—
Debian:13(1)
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
—
Debian:14(1)
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
—

Weakness Classification(1)

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

Data Freshness Timeline

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

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-17877?
CVE-2026-17877 is a high-severity vulnerability; its CVE record was published on July 30, 2026. Inappropriate implementation in Chromoting in Google Chrome on Linux prior to 151.0.7922.72 allowed a local attacker to perform OS-level privilege escalation via malicious network traffic. (Chromium security severity: Medium)
When was the CVE record for CVE-2026-17877 published?
The CVE record for CVE-2026-17877 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-17877 actively exploited?
CVE-2026-17877 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (2nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-17877?
CVE-2026-17877 has a CVSS v3.1 base score of 8.4 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-17877?
A fix for CVE-2026-17877 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-17877 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-17877

Explore →

Is Your Infrastructure Affected by CVE-2026-17877?

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

Book a Demo →Browse All CVEs