NetScaler ADC End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all NetScaler ADC versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
Running an EOL version? Get matched with support options — free ↓
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/netscaler-adc)
NetScaler ADC lifecycle status — the real story
NetScaler ADC (named Citrix NetScaler until 2018, Citrix ADC from 2018, and NetScaler again since 2023 under Cloud Software Group) is the application delivery controller and gateway behind the CitrixBleed exploitation waves — an edge product squarely inside the scope of CISA’s BOD 26-02 crackdown on end-of-support edge devices. Lifecycle dates are fixed per firmware release line and published in the Citrix Product Matrix, with two milestones: End of Maintenance (EOM — our active-support column) and End of Life (EOL). Per the NetScaler firmware release-cycle policy, from 14.1 onward each line gets a seven-year cycle: feature releases in years 1–3, maintenance releases in years 4–6, and technical support only in year 7 until EOL.
The clock that matters now: 13.1 reaches End of Maintenance on September 15, 2026 — and End of Life September 15, 2027, with the matrix noting optional extended support for eligible customers (contact Citrix). The 13.0 and 12.1 lines — the branches hit hardest in the CitrixBleed era — are already past End of Life (July 15, 2024 and May 30, 2023 respectively). Compliance variants carry their own dates on the matrix: 12.1 NDcPP (EOM 2023-12-31, EOL 2024-12-31), 12.1 FIPS (EOM 2024-12-31, EOL 2025-12-31), and 13.1 FIPS (same dates as standard 13.1). Firmware lines older than 12.1 no longer appear on the matrix at all.
These dates are vendor-declared, read from the Citrix Product Matrix (a static page we can re-verify automatically). One trap the record should note: NetScaler Console (formerly ADM) 13.1 is a different product with different dates — never conflate it with ADC firmware 13.1.
NetScaler ADC release and support pattern
Across the 4 release lines with a published release date, NetScaler ADC has shipped a new line roughly every 1.9 years (median interval). A line typically stays supported for about 5.6 years from its release to its end-of-life date.
Of the 4 release lines tracked, 2 are past end of life and 2 are still within support. The newest line, 14.1, was released August 8, 2023. The next scheduled end of life is 13.1 on September 15, 2027 — 378 days from this build. The longest-supported line currently published is 14.1, to August 8, 2030.
Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.
NetScaler ADC security intelligence
CISA KEV history: NetScaler ADC is named in CISA's Known Exploited Vulnerabilities catalog 7 times, most recently on 2026-08-26, including use in ransomware campaigns. Derived from CISA's live catalog at every build.
What does NetScaler ADC end of life mean for your organization?
When a version of NetScaler ADC 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 NetScaler ADC 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 NetScaler ADC 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 NetScaler ADC versions. This is a bridge, not a permanent solution — plan your migration in parallel.
NetScaler ADC has 2 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 NetScaler ADC 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."