CVE-2026-19315

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.5% (37th 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 a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 9.3Exploit: None knownExposed services: Not assessed

Fireware OS 2026.3.1, Fireware OS 2026.2.2, Fireware OS 12.12.2, Fireware OS 12.5.20 (from the CVE record's solution, WatchGuard Technologies, Inc.) — apply it.

A type confusion vulnerability in the iked process of WatchGuard Fireware OS allows a remote unauthenticated attacker to execute arbitrary code by sending specially crafted network traffic.

CVSS v3
9.3
EG Score
9.3CRITICALmedium confidence
EG Risk
57
EG Risk 57/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.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (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: Fireware OS 2026.3.1, Fireware OS 2026.2.2, Fireware OS 12.12.2, Fireware OS 12.5.20 (from the CVE record's solution, WatchGuard Technologies, Inc.). Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
37th
KEV
Not listed

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

Fireware OS 2026.3.1, Fireware OS 2026.2.2, Fireware OS 12.12.2, Fireware OS 12.5.20 (from the CVE record's solution, WatchGuard Technologies, Inc.). Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (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)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (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 27, 2026

Last Modified

September 3, 2026

Advisory Details (1)

Auto-updated Oct 3, 2026
Fix named in the CVE record's solution (WatchGuard Technologies, Inc.).
Web page

CVE-2026-19315 — Fireware OS Pre-Authentication Type Confusion in iked Allows Remote Code Execution

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

Vendor Advisories for CVE-2026-19315(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 28× in last 7d / 172× 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 309 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 209 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-19315?
CVE-2026-19315 is a critical-severity vulnerability; its CVE record was published on August 27, 2026. A type confusion vulnerability in the iked process of WatchGuard Fireware OS allows a remote unauthenticated attacker to execute arbitrary code by sending specially crafted network traffic.
When was CVE-2026-19315 made public?
CVE-2026-19315 was made public on August 27, 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 27, 2026. EchelonGraph's copy of the record carries a last-modified date of September 3, 2026; the record at its source may have been updated since.
Is CVE-2026-19315 actively exploited?
CVE-2026-19315 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (37th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-19315?
CVE-2026-19315 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-19315?
The CVE record's solution for CVE-2026-19315, written by its CNA WatchGuard Technologies, Inc., names the fix: "Fireware OS 2026.3.1, Fireware OS 2026.2.2, Fireware OS 12.12.2, Fireware OS 12.5.20". The vendor advisories EchelonGraph has for CVE-2026-19315 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-19315?

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

Book a Demo →Browse All CVEs