SonicWall Email Security End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all SonicWall Email Security versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
SonicWall Email Security 10.0.36 is supported until April 30, 2027, its end-of-support date. Active support for SonicWall Email Security 10.0.36 ends on August 12, 2026; security fixes continue until that end-of-life date. It is also the next SonicWall Email Security version to reach end of life. 31 of 34 tracked SonicWall Email Security versions are past end of life; the most recent to reach it, 10.0.34, did so on June 1, 2026. The full SonicWall Email Security lifecycle, with every version's release and end-of-support date, is in the table below.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 7.0-7.3.0 | 7.0-7.3.0 | Dec 18, 2008 | Sep 1, 2014 | 4391 days past EOL | EOL |
| 7.4.0-7.4.5 | 7.4.0-7.4.5 | Jun 21, 2012 | Nov 7, 2015 | 3959 days past EOL | EOL |
| 7.4.6-7.4.9 | 7.4.6-7.4.9 | Mar 10, 2014 | Mar 10, 2016 | 3835 days past EOL | EOL |
| 8.0-8.0.1 | 8.0-8.0.1 | Apr 24, 2014 | Jul 11, 2016 | 3712 days past EOL | EOL |
| 8.0.3-8.0.4 | 8.0.3-8.0.4 | Sep 22, 2014 | Sep 30, 2016 | 3631 days past EOL | EOL |
| 8.0.5-8.3.2 | 8.0.5-8.3.2 | Sep 30, 2016 | Sep 30, 2018 | 2901 days past EOL | EOL |
| 9.0.0-9.2.2 | 9.0.0-9.2.2 | Jan 14, 2019 | Jan 14, 2021 | 2064 days past EOL | EOL |
| 10.0.1 | 10.0.1 | Apr 24, 2019 | Apr 24, 2021 | 1964 days past EOL | EOL |
| 10.0.2 | 10.0.2 | Jun 24, 2019 | Jun 24, 2021 | 1903 days past EOL | EOL |
| 10.0.3-10.0.4 | 10.0.3-10.0.4 | Nov 22, 2019 | May 22, 2021 | 1936 days past EOL | EOL |
| 10.0.5 | 10.0.5 | Jan 8, 2020 | Jul 8, 2021 | 1889 days past EOL | EOL |
| 10.0.6-10.0.7 | 10.0.6-10.0.7 | Feb 21, 2020 | Aug 21, 2021 | 1845 days past EOL | EOL |
| 10.0.8 | 10.0.8 | Sep 18, 2020 | Mar 18, 2022 | 1636 days past EOL | EOL |
| 10.0.9 | 10.0.9 | Apr 19, 2021 | Apr 19, 2022 | 1604 days past EOL | EOL |
| 10.0.10 | 10.0.10 | Jun 3, 2021 | Jun 3, 2022 | 1559 days past EOL | EOL |
| 10.0.11 | 10.0.11 | Nov 1, 2021 | Jan 11, 2022 | 1702 days past EOL | EOL |
| 10.0.12 | 10.0.12 | Dec 14, 2021 | Dec 14, 2022 | 1365 days past EOL | EOL |
| 10.0.13 | 10.0.13 | Dec 22, 2021 | Dec 22, 2022 | 1357 days past EOL | EOL |
| 10.0.15 | 10.0.15 | Jan 5, 2022 | Jan 5, 2023 | 1343 days past EOL | EOL |
| 10.0.16 | 10.0.16 | Feb 10, 2022 | Feb 10, 2023 | 1307 days past EOL | EOL |
| 10.0.17 | 10.0.17 | Apr 18, 2022 | Apr 18, 2023 | 1240 days past EOL | EOL |
| 10.0.19 | 10.0.19 | Aug 1, 2022 | Aug 1, 2023 | 1135 days past EOL | EOL |
| 10.0.21 | 10.0.21 | Feb 1, 2023 | Jun 1, 2026 | 100 days past EOL | EOL |
| 10.0.24 | 10.0.24 | Jun 13, 2023 | Jun 1, 2026 | 100 days past EOL | EOL |
| 10.0.25 | 10.0.25 | Sep 28, 2023 | Jun 1, 2026 | 100 days past EOL | EOL |
| 10.0.26 | 10.0.26 | Nov 8, 2023 | Jun 1, 2026 | 100 days past EOL | EOL |
| 10.0.28 | 10.0.28 | Mar 12, 2024 | Jun 1, 2026 | 100 days past EOL | EOL |
| 10.0.29 | 10.0.29 | Apr 18, 2024 | Jun 1, 2026 | 100 days past EOL | EOL |
| 10.0.30 | 10.0.30 | Jun 6, 2024 | Jun 1, 2026 | 100 days past EOL | EOL |
| 10.0.31 | 10.0.31 | Dec 13, 2024 | Apr 30, 2027 | 233 days remaining | Active |
| 10.0.33 | 10.0.33 | Aug 11, 2025 | Jun 1, 2026 | 100 days past EOL | EOL |
| 10.0.34 | 10.0.34 | Nov 20, 2025 | Jun 1, 2026 | 100 days past EOL | EOL |
| 10.0.35 | 10.0.35 | Mar 31, 2026 | Apr 30, 2027 | 233 days remaining | Active |
| 10.0.36 | 10.0.36 | Aug 11, 2026 | Apr 30, 2027 | 233 days remaining | Active |
[](https://endoflife.ai/sonicwall-email-security)
SonicWall Email Security lifecycle status — the real story
SonicWall Email Security (the on-premises secure email gateway software, virtual appliance and hosted-appliance firmware) lifecycle from SonicWall's own Product Lifecycle Tables (the 'Email Security' section, Software table; read 2026-09-09). Mapping: releaseDate = Software Release Date, support = Limited Support Date (the line enters limited support), eol = Support Discontinued Date. All 34 versioned software lines included, from 7.0-7.3.0 (2008) through 10.0.36 (released 2026-08-11); the 'Anti-Spam Desktop (All versions)' row is a client product and is left out. Version ranges are kept as SonicWall publishes them (for example 8.0.5-8.3.2 is one row on their table).
Vendor anomaly kept verbatim, not corrected: the 10.0.11 row states Limited Support 2022-05-01 but Support Discontinued 2022-01-11, four months earlier; the table is the source of record and the row is reproduced as published.
KEV context (CISA catalog 2026.09.08, product string 'SonicWall Email Security'): CVE-2021-20021, CVE-2021-20022 and CVE-2021-20023 (all added 2021-11-03, all flagged known ransomware campaign use) - the April 2021 zero-day chain against on-premises Email Security 10.0.9 and earlier. No version scoping is asserted from this page; the score uses the catalog join only.
The appliance hardware those versions run on (ES 5000/7000/9000 series and retired models) is the separate sonicwall-email-security-appliances page.
SonicWall Email Security release and support pattern
Of the 34 release lines tracked, 31 are past end of life and 3 are still within support. The newest line, 10.0.36, was released August 11, 2026. The next scheduled end of life is 10.0.36 on April 30, 2027 — 233 days from this build. The longest-supported line currently published is 10.0.31, to April 30, 2027.
Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.
SonicWall Email Security security intelligence
CISA KEV history: SonicWall Email Security is named in CISA's Known Exploited Vulnerabilities catalog 3 times, most recently on 2021-11-03, including use in ransomware campaigns. Derived from CISA's live catalog at every build.
What does SonicWall Email Security end of life mean for your organization?
When a version of SonicWall Email Security 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 Email Security 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 Email Security 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.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Buy extended support | Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application | A bridge, not a destination — every year purchased is a year the migration still has to happen |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
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 Email Security versions. This is a bridge, not a permanent solution — plan your migration in parallel.
SonicWall Email Security has 31 versions past end of life — security patches have stopped, but CVE disclosures haven't. Extended support past the official date exists for many products in this position — whether it exists for SonicWall Email Security is exactly what we check. Tell us where to reach you and we'll reply with matched options and pricing guidance — or an honest "no vendor covers this."