QNAP NAS End of Life (EOL) Dates & Support Timeline

QNAP NAS lifecycle status — the real story

QNAP NAS and expansion units (the 'NAS / Expansion' product line, 466 models) from the JSON behind QNAP's own Product Support Status page, generated by tools/qnap-lifecycle.mjs (read 2026-09-09). Mapping: eol = the vendor's 'Technical Support and Security Updates' end - a full date as given, a month as the last day of that month (the same month-end convention as our Ubuntu feed), the vendor's word 'EOL' as end of life with no published day; support = the 'OS and Application Updates and Maintenance' end (Full = still maintained; a month with the final OS version, carried as lastOsVersion); the vendor's successor model is carried. Release dates are not in the API and are left null. Other QNAP lines on the same page (switches, QVR surveillance appliances, routers, adapters, accessories) are not modelled here.

As read: 198 of 466 models are past the end of security updates (95 of them with no day published, only 'EOL' and the month their OS updates stopped), 141 carry a future or past date, and 230 are active. QNAP's own policy text: EOL models receive only high or critical security updates until the Technical Support and Security Updates date, then nothing.

KEV context (CISA catalog 2026.09.08): CISA files QNAP NAS exploitation under 'Network Attached Storage (NAS)' and 'QNAP Network-Attached Storage (NAS)' (CVE-2018-19943, CVE-2018-19949, CVE-2018-19953, CVE-2020-2509, CVE-2021-28799, the QLocker and eCh0raix ransomware waves), under 'QTS' (CVE-2019-7193) and under 'Photo Station' (CVE-2019-7192, CVE-2019-7194, CVE-2019-7195, CVE-2022-27593, the DeadBolt wave) - QTS is the operating system these appliances run and Photo Station is a QTS application, so the QTS and Photo Station entries are joined by a force override. The VioStor NVR and Helpdesk entries are other products and are not joined. No per-model scoping is asserted.

Refreshed 2026-10-07 from the same API (468 models): three models (TS-877, TS-EC1680U R2, TS-EC2480U R2) carried the vendor typo 1907-12-31 and sixteen expansion units flagged is_eol with N/A update columns were served as active; the adapter now rejects years outside 2000-2100 and serves QNAP EOL flag (eol true, no published day) whenever no usable date is printed. New models ES1686Adc and TS-h966TX added; TS-h973AX successor TS-h966TX.

QNAP NAS release and support pattern

Of the 468 release lines tracked, 213 are past end of life and 255 are still within support; 113 are marked end of life without a published date. The next scheduled end of life is ES1686dc on December 31, 2026 — 75 days from this build. The longest-supported line currently published is TS-1635, to December 31, 2028.

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

QNAP NAS security intelligence

CISA KEV history: QNAP NAS is named in CISA's Known Exploited Vulnerabilities catalog 10 times, most recently on 2022-09-08, including use in ransomware campaigns. Derived from CISA's live catalog at every build.

What does QNAP NAS end of life mean for your organization?

When a version of QNAP 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 QNAP 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 QNAP 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.

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 QNAP NAS versions. This is a bridge, not a permanent solution — plan your migration in parallel.

Related Products