CVE-2026-78174

CRITICALPre-NVD 9.39.3
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (35th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 3 sources updated this week
9.3EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 9.3Exploit: None knownExposed services: Not assessed

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

WatchGuard Dimension records unredacted session identifiers for logged-in users in its web UI diagnostic log. A low-privileged Dimension Administrator can retrieve this log and extract a Super Administrator's session token while that administrator is logged in, enabling account takeover.

CVSS v3
9.3
EG Score
9.3CRITICALmedium confidence
EG Risk
42
EG Risk 42/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)
Severity93% × 45%
The EG Score, 9.3 of 10.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CVSS v4.0 confidentiality and integrity impact both High). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.4%
EPSS %ILE
35th
KEV
Not listed

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

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CVSS v4.0 confidentiality and integrity impact both High). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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's BOD 26-04 default) · Technical impact total (CVSS v4.0 confidentiality and integrity impact both High). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” 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 27, 2026

Last Modified

August 28, 2026

Advisory Details (1)

Auto-updated Oct 7, 2026
No fix on record yet.
Web page

CVE-2026-78174 — WatchGuard Dimension Session Hijack via Exposed Session Tokens in Diagnostic Logs

https://psirt.watchguard.com/CVE-2026-78174

Vendor Advisories for CVE-2026-78174(1)

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

Weakness Classification(3)

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

Data Freshness Timeline

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

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-78174?
CVE-2026-78174 is a critical-severity vulnerability; its CVE record was published on August 27, 2026. WatchGuard Dimension records unredacted session identifiers for logged-in users in its web UI diagnostic log. A low-privileged Dimension Administrator can retrieve this log and extract a Super Administrator's session token while that administrator is logged in, enabling account takeover.
When was the CVE record for CVE-2026-78174 published?
The CVE record for CVE-2026-78174 was published on August 27, 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 28, 2026; the record at its source may have been updated since.
Is CVE-2026-78174 actively exploited?
CVE-2026-78174 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (35th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-78174?
CVE-2026-78174 has a CVSS base score of 9.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-78174?
No fix for CVE-2026-78174 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-78174 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-78174?

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

Book a Demo →Browse All CVEs