CVE-2026-57909

CRITICALPre-NVD 9.49.4
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (33rd 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.4EG
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.4Exploit: None knownExposed services: Not assessed

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

The CVE record's CNA (WatchGuard Technologies, Inc.) lists WatchGuard Agent versions before 1.25.13.0000 as affected. No release containing a fix is confirmed on record.

A path traversal vulnerability in WatchGuard Agent allows a remote, unauthenticated attacker on an adjacent network to execute arbitrary code on an affected system.

CVSS v3
9.4
EG Score
9.4CRITICALmedium 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)
Severity94% × 45%
The EG Score, 9.4 of 10.
Exploitation0.4% × 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: 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
33rd
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 (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

August 25, 2026

Last Modified

September 28, 2026

Advisory Details (1)

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

CVE-2026-57909 — WatchGuard Agent path traversal allows unauthenticated remote code execution

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

Vendor Advisories for CVE-2026-57909(1)

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

Weakness Classification(2)

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

Data Freshness Timeline

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

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-57909?
CVE-2026-57909 is a critical-severity vulnerability; its CVE record was published on August 25, 2026. A path traversal vulnerability in WatchGuard Agent allows a remote, unauthenticated attacker on an adjacent network to execute arbitrary code on an affected system.
When was CVE-2026-57909 made public?
CVE-2026-57909 was made public on August 25, 2026: that is the date its CVE record's CNA, WatchGuard Technologies, Inc., gives for when the vulnerability was made public. The CVE record itself was published on August 25, 2026. EchelonGraph's copy of the record carries a last-modified date of September 28, 2026; the record at its source may have been updated since.
Is CVE-2026-57909 actively exploited?
CVE-2026-57909 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (33rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-57909?
CVE-2026-57909 has a CVSS base score of 9.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-57909?
No fix for CVE-2026-57909 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 CVE record's CNA (WatchGuard Technologies, Inc.) lists WatchGuard Agent versions before 1.25.13.0000 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-57909 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-57909?

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

Book a Demo →Browse All CVEs