CVE-2026-78892

HIGHPre-NVD 7.17.1
EchelonGraph scoreMEDIUM confidence

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

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

Triggered by: GitHub Security Advisory CVSS
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS, GitHub Security Advisory
Trending — 4 sources updated this week
7.1EG
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: 7.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Incorrect authorization in Chromoting in Google Chrome on on Windows prior to 152.0.7977.65 allowed a local attacker to bypass system access restrictions via a local program. (Chromium security severity: Medium)

CVSS v3
7.1
Vendor severity
MEDIUMper Google (Chromium)Vendor's own band, not a CVSS rating — advisory text: (Chromium security severity: Medium)
EG Score
7.1HIGHmedium confidence
EG Risk
32
EG Risk 32/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)
Severity71% × 45%
The EG Score, 7.1 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 every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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
1st
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

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

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

August 25, 2026

Last Modified

August 31, 2026

Advisory Details (2)

Auto-updated Aug 28, 2026
Patch available.
Web page

Chromium

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

Chrome Releases: Stable Channel Update for Desktop

https://chromereleases.googleblog.com/2026/08/stable-channel-update-for-desktop_0256176589.html

Vendor Advisories for CVE-2026-78892(2)

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

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
chromium113.0.5672.126-1 ... 152.0.7977.64-1 (412 versions)
  • every version up to 152.0.7977.75-1~deb12u1: fixed in 152.0.7977.75-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
chromium138.0.7204.183-1 ... 152.0.7977.75-1~deb12u1 (178 versions)
  • every version up to 152.0.7977.75-1~deb13u1: fixed in 152.0.7977.75-1~deb13u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
chromium138.0.7204.183-1 ... 151.0.7922.71-1~deb13u1 (176 versions)
  • every version up to 152.0.7977.64-1: fixed in 152.0.7977.64-1
—

Weakness Classification(1)

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

Data Freshness Timeline

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

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-78892?
CVE-2026-78892 is a high-severity vulnerability; its CVE record was published on August 25, 2026. Incorrect authorization in Chromoting in Google Chrome on on Windows prior to 152.0.7977.65 allowed a local attacker to bypass system access restrictions via a local program. (Chromium security severity: Medium)
When was the CVE record for CVE-2026-78892 published?
The CVE record for CVE-2026-78892 was published on August 25, 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 31, 2026; the record at its source may have been updated since.
Is CVE-2026-78892 actively exploited?
CVE-2026-78892 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-78892?
CVE-2026-78892 has a CVSS v3.1 base score of 7.1 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-78892?
A fix for CVE-2026-78892 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-78892 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-78892

Explore →

Is Your Infrastructure Affected by CVE-2026-78892?

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

Book a Demo →Browse All CVEs