WatchGuard XTM 26 end-of-life and support dates
WatchGuard XTM 26 reached end of support on 2021-07-01. That was 1958 days ago. Active support ended on 2016-07-01.
Scope: hardware modelListed under WatchGuard Firebox / FirewareAs of 2026-11-10
Lifecycle timeline
- 2016-07-01 — End of active support · End of maintenance
- 2021-07-01 — End of support · End of standard support
When is WatchGuard XTM 26 end of life?
WatchGuard XTM 26 reached end of support on 2021-07-01. Active support ended on 2016-07-01.
Source: WatchGuard End-of-Life Policy
Is WatchGuard XTM 26 still supported?
No. Support ended on 2021-07-01.
Source: WatchGuard End-of-Life Policy
Why this status?
“End of active support” (end-of-maintenance, 2016-07-01, confirmed) has passed and no later support phase is published.
Other Firebox / Fireware models still inside the support window
- Firebox T15 — support ends 2027-03-01
- Firebox T15-W — support ends 2027-03-01
- Firebox T20 — support ends 2028-07-01
- Firebox T20-W — support ends 2028-07-01
The cited source lists these as still supported. They are not a replacement recommendation; check WatchGuard's guidance for your deployment before planning change work.
Evidence
- WatchGuard End-of-Life Policy Official · checked 2026-07-15
Related
- All WatchGuard Firebox / Fireware lifecycle dates· 60 tracked models
- WatchGuard Firebox / Fireware security advisories· 87 tracked
- CVE-2026-98432: WatchGuard Linux Kernel IPv4 Use-After-Free Vulnerability (CVE-2026-98432)
- CVE-2026-112709: WatchGuard Fireware OS Heap Buffer Overflow in AD Authentication Service Allows Pre-Authentication Remote Code Execution
- CVE-2026-103593: WatchGuard Fireware OS Stack Buffer Overflow in Logging Service Allows Remote Code Execution
- CVE-2026-112710: WatchGuard Fireware OS Heap Buffer Overflow in AD Authentication Service Allows Pre-Authentication Remote Code Execution
- CVE-2026-93857: WatchGuard Fireware OS Pre-Authentication Stack Buffer Overflow in SIP Proxy Allows Remote Code Execution
- CVE email alerts for WatchGuard
Status is calculated from the published milestones. When a vendor does not publish a date, this page says so and does not estimate one.