Zyxel NAS End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Zyxel NAS versions. Dates read at the vendor's own lifecycle pages (zyxel.com). Updated at every deploy.
Every tracked Zyxel NAS version is past end of life; the most recent to reach it, NAS326, did so on December 31, 2023. The full Zyxel NAS lifecycle, with every version's release and end-of-support date, is in the table below.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| NAS540 | 5.21(AATB.11)C0 | — | May 30, 2023 | 1245 days past EOL | EOL |
| NAS542 | V5.21(ABAG.15)C0 | — | Dec 31, 2023 | 1030 days past EOL | EOL |
| NAS326 | V5.21(AAZF.18)C0 | — | Dec 31, 2023 | 1030 days past EOL | EOL |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/zyxel-nas)
Zyxel NAS lifecycle status — the real story
Zyxel NAS appliances (NAS326, NAS540, NAS542) from Zyxel's global End-of-Life page (the same JS-rendered table the zyxel-usg firewall page reads; read 2026-09-09 in a browser). Zyxel publishes three milestones and we map them in the same order as the firewall page: support = End of Development, eol = End of Vulnerability Support (no more security fixes), extendedSupport = End of Life (all hardware and firmware support ceases). All three models are past every milestone: NAS540 ended vulnerability support 2023-05-30 and life 2023-11-30; NAS326 and NAS542 ended vulnerability support 2023-12-31 and life 2024-06-30. latest = the 'latest firmware' string Zyxel prints per model. Release dates are not published and are left null. Older NAS models (the NSA series) have been moved to Zyxel's archived EOL PDF, which lists models more than three years past end of life, and are not modelled here.
KEV context (CISA catalog 2026.09.08): CVE-2020-9054 (added 2022-03-25) and CVE-2023-27992 (added 2023-06-23) under 'Multiple Network-Attached Storage (NAS) Devices', matched on the display name. Zyxel's 2024 NAS326/NAS542 advisories (CVE-2024-29972 through 29976) were issued as post-EOL hotfixes and are not in the catalog. No per-model scoping is asserted.
Zyxel NAS release and support pattern
Of the 3 release lines tracked, 3 are past end of life and 0 are still within support. Upstream also publishes an extended-support phase for 3 lines, shown in the table above.
Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.
Zyxel NAS security intelligence
CISA KEV history: Zyxel NAS is named in CISA's Known Exploited Vulnerabilities catalog 2 times, most recently on 2023-06-23. Derived from CISA's live catalog at every build.
What does Zyxel NAS end of life mean for your organization?
When a version of Zyxel NAS 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: A CVE-based scan does not show the accumulation of unpatched vulnerabilities in EOL software. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no vendor patch is coming. This is one of the most dangerous gaps in enterprise security posture.
Organizations running EOL Zyxel NAS 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 Zyxel NAS 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 |
| Commercial extended support | Not available for Zyxel NAS from the original maintainer | Third-party vendors patch some end-of-life software on a custom basis; availability depends on the specific version and source access |
| 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.
Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.
Open Stack Scanner →