Juniper Junos OS End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Juniper Junos OS versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 20.2 | 20.2 | Jun 30, 2020 | Dec 30, 2023 | 976 days past EOL | EOL |
| 20.3 | 20.3 | Sep 29, 2020 | Mar 29, 2023 | 1252 days past EOL | EOL |
| 20.4 | 20.4 | Dec 25, 2020 | Jun 25, 2024 | 798 days past EOL | EOL |
| 21.1 | 21.1 | Mar 25, 2021 | Sep 25, 2023 | 1072 days past EOL | EOL |
| 21.2 | 21.2 | Jun 29, 2021 | Dec 29, 2024 | 611 days past EOL | EOL |
| 21.3 | 21.3 | Sep 23, 2021 | Mar 23, 2024 | 892 days past EOL | EOL |
| 21.4 | 21.4 | Dec 20, 2021 | Jun 20, 2025 | 438 days past EOL | EOL |
| 22.1 | 22.1 | Mar 24, 2022 | Sep 24, 2024 | 707 days past EOL | EOL |
| 22.2 | 22.2 | Jun 23, 2022 | Dec 23, 2025 | 252 days past EOL | EOL |
| 22.3 | 22.3 | Sep 28, 2022 | Mar 28, 2025 | 522 days past EOL | EOL |
| 22.4 | 22.4 | Dec 22, 2022 | Jun 22, 2026 | 71 days past EOL | EOL |
| 23.1 | 23.1 | Mar 31, 2023 | Mar 31, 2024 | 884 days past EOL | EOL |
| 23.2 | 23.2 | Jun 23, 2023 | Dec 23, 2028 | 844 days remaining | Active |
| 23.4 | 23.4 | Dec 26, 2023 | Jun 26, 2029 | 1029 days remaining | Active |
| 24.2 | 24.2 | Jul 19, 2024 | Jan 19, 2030 | 1236 days remaining | Active |
| 24.4 | 24.4 | Dec 29, 2024 | Jun 29, 2030 | 1397 days remaining | Active |
| 25.2 | 25.2 | Jun 30, 2025 | Dec 30, 2030 | 1581 days remaining | Active |
| 25.4 | 25.4 | Dec 22, 2025 | Jun 22, 2031 | 1755 days remaining | Active |
| 26.2 | 26.2 | Jun 29, 2026 | Dec 29, 2031 | 1945 days remaining | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/junos)
Juniper Junos OS lifecycle status — the real story
Junos OS runs Juniper’s routers, switches and SRX firewalls — network-boundary infrastructure squarely in scope for CISA’s BOD 26-02 discipline on end-of-support edge devices, and a platform whose SRX/EX vulnerabilities have reached CISA’s Known Exploited Vulnerabilities catalog. Juniper publishes a complete, dated lifecycle table (“Junos OS Dates & Milestones”): every release gets a First Revenue Ship date, an End of Engineering date (our active-support column) and an End of Support date, consistently six months after End of Engineering.
The policy has a two-tier rhythm worth knowing: releases are typed EOL (standard, roughly two years of engineering) or EEOL — Extended End of Life — and from Junos 23.2 onward EEOL releases get five years of engineering from ship date (21.2–22.4-era EEOL got three). In practice the x.2 and x.4 releases carry the EEOL designation and are the lines to standardize on — the same role LTS plays elsewhere, under Juniper’s own vocabulary. Recently passed: 22.4 (the last 22.x line) reached End of Support on June 22, 2026, and 22.2 on December 23, 2025; everything 23.1 and older on the standard track is already out of support.
Dates here are vendor-declared, read from Juniper’s support portal (a JavaScript-rendered page — re-verification requires a browser). Juniper’s numbering skips some quarters (there are no 23.3, 24.1 or 24.3 releases — not gaps in our data), and the portal’s table reaches back to Junos 5.0 for archaeology; this page tracks 20.2 onward.
Juniper Junos OS release and support pattern
Across the 19 release lines with a published release date, Juniper Junos OS has shipped a new line roughly every 3 months (median interval). A line typically stays supported for about 3.5 years from its release to its end-of-life date.
Of the 19 release lines tracked, 12 are past end of life and 7 are still within support. The newest line, 26.2, was released June 29, 2026. The next scheduled end of life is 23.2 on December 23, 2028 — 843 days from this build. The longest-supported line currently published is 26.2, to December 29, 2031.
Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.
Juniper Junos OS security intelligence
CISA KEV history: Juniper Junos OS is named in CISA's Known Exploited Vulnerabilities catalog 7 times, most recently on 2025-03-13. Derived from CISA's live catalog at every build.
What does Juniper Junos OS end of life mean for your organization?
When a version of Juniper Junos OS 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 Juniper Junos OS 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 Juniper Junos OS 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 Juniper Junos OS versions. This is a bridge, not a permanent solution — plan your migration in parallel.
Juniper Junos OS has 12 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 Juniper Junos OS 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."