SonicWall SonicOS End of Life (EOL) Dates & Support Timeline

SonicWall SonicOS lifecycle status — the real story

SonicOS is the firmware on SonicWall’s TZ, NSa and NSsp firewalls — internet-facing edge devices of exactly the class CISA’s BOD 26-02 orders end-of-support discipline for, and a platform with its own history of exploited SSL-VPN vulnerabilities. SonicWall publishes lifecycle dates per firmware release, not per major version, on its Product Lifecycle Tables: each release row carries a release date, a status (Feature/Maintenance/General Release), an End of Support date once assigned, and a recommended upgrade path.

The date to circle: SonicOS 7.3.0, 7.3.1, 7.3.2 and the 7.0.1-5169 maintenance build all reach End of Support on September 30, 2026 — the same day as a remarkable cluster of other deadlines (Microsoft Project Online’s retirement and FortiOS 7.2’s end of support among them). SonicWall’s stated upgrade path is 7.3.2-and-later on Gen 7 hardware; 7.3.3 currently carries no End of Support date. The earlier 7.1.x/7.0.x releases hit End of Support on September 30, 2025, and the Gen 6 6.x line (through 6.5.4.15) on February 4, 2025 — with 6.5.5.1 and 5.9.2.14 kept as active releases for older hardware generations.

Provenance nuances worth stating plainly: for retired lines that SonicWall lists as combined rows (“7.1.x and 7.0.X”, “6.5.4.15 and Older 6.x versions”, “5.9.2.13 and older”), the release date shown is the date on SonicWall’s lifecycle record — the vendor does not publish original launch dates for those lines on this page, so treat the End of Support column as the authoritative one. Separately, SonicWall’s hardware lifecycle uses a five-phase model (Last Order Day → Active Retirement → Limited Retirement → 1-Year Support Last Order → End of Support); among Gen 6 firewalls, TZ400 and TZ600 passed hardware End of Support on August 1, 2026, with TZ350 and TZ500 following October 1, 2026.

SonicWall SonicOS release and support pattern

Across the 11 release lines with a published release date, SonicWall SonicOS has shipped a new line roughly every 3 months (median interval). A line typically stays supported for about 1 year from its release to its end-of-life date (measured on the 8 lines with both dates published).

Of the 11 release lines tracked, 4 are past end of life and 7 are still within support. The newest line, 7.3.3, was released May 27, 2026. The next scheduled end of life is 7.3.2 on September 30, 2026 — 28 days from this build. The longest-supported line currently published is 7.0.1-5169, to September 30, 2026.

Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.

SonicWall SonicOS security intelligence

CISA KEV history: SonicWall SonicOS is named in CISA's Known Exploited Vulnerabilities catalog 3 times, most recently on 2025-02-18, including use in ransomware campaigns. Derived from CISA's live catalog at every build.

What does SonicWall SonicOS end of life mean for your organization?

When a version of SonicWall SonicOS reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.

The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.

Organizations running EOL SonicWall SonicOS should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.

Your options when SonicWall SonicOS reaches end of life

There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.

How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.

Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.

Formalizing decisions like this across your estate? Our free EOL policy template is a ready-to-adopt policy with risk tiers, remediation SLAs, and audit mapping — no signup, free to use and share.

Extended Support Options

If you cannot migrate immediately, extended support vendors provide continued security patches for EOL SonicWall SonicOS versions. This is a bridge, not a permanent solution — plan your migration in parallel.

Related Products