Juniper SRX Series (hardware) End of Life (EOL) Dates & Support Timeline

Juniper SRX Series (hardware) lifecycle status — the real story

Juniper SRX Series is the hardware under Junos OS on the firewall side: the branch SRX100 to SRX650 generations, the SRX300 line, the mid-range SRX1400, SRX1500, SRX4100 and SRX4200, and the SRX3000 and SRX5000 chassis. Cycles on this page are appliance models, so it is the hardware companion to the Junos OS software page: the exploited CVEs that put Junos in CISA's KEV catalog are software CVEs and are tracked there, but they run on these boxes. Every date comes from Juniper's own SRX Series Hardware Dates and Milestones page (public, no login, a static table), re-checked at every build. That page is SKU-level; this page maps each vendor row to the model it describes, and the SKUs behind each cycle are listed in its release column. Subscription, licence, cable, transceiver and vSRX rows on the vendor page are deliberately not modelled here.

Field mapping: support is Juniper's Last Order date; eol is Juniper's End of Support, after which no support is available for the hardware. The announcement date and, where Juniper publishes one, the End of Engineering date (newer rows) or the Same Day Support Discontinued date (older rows) are carried as extra fields, with the Technical Support Bulletin number where the page gives it. Where Juniper lists a TAA variant with a later End of Support than the base model, the base model's date is used and the variant's date is noted on the cycle.

The dates that matter now. The SRX1500 and SRX4100 systems were announced end of life on October 15, 2025 with a last order date of April 15, 2026, End of Engineering on April 15, 2029 (Junos 26.2 is the last software version) and End of Support on April 15, 2031. The SRX5400, SRX5600 and SRX5800 chassis generation with the RE-1800X4 routing engine left order on August 30, 2022 and reaches End of Support on September 15, 2027. The SRX550M ends on March 15, 2028. Already past support: the SRX550, SRX220H2 and SRX110H2 on November 30, 2024; the SRX650, SRX240H2, SRX210HE2 and SRX100H2 on December 31, 2022 (their TAA variants on November 30, 2024); the SRX1400 on December 1, 2023; the first-generation SRX5600 and SRX5800 on December 31, 2022; the SRX3400 and SRX3600 on November 30, 2019; and the original SRX100 to SRX240 branch models on May 10, 2019.

Current models named on the same vendor page with no hardware end-of-life row yet, the SRX300, SRX320, SRX340, SRX345, SRX380, SRX4200 and SRX4600, are carried without dates, which the EOS Edge Device feed reports as no date announced. Under CISA BOD 26-02 every SRX model past its End of Support date is an end-of-support edge device regardless of the Junos release it runs.

Juniper SRX Series (hardware) release and support pattern

Of the 31 release lines tracked, 18 are past end of life and 13 are still within support. The next scheduled end of life is SRX5800 on September 15, 2027 — 331 days from this build. The longest-supported line currently published is SRX1500, to April 15, 2031.

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

What does Juniper SRX Series (hardware) end of life mean for your organization?

When a version of Juniper SRX Series (hardware) 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 Juniper SRX Series (hardware) 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 SRX Series (hardware) 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, check whether the vendor or a third party sells extended support with security patches for your Juniper SRX Series (hardware) version; coverage varies by product and version. Where it exists it is a bridge, not a permanent solution — plan your migration in parallel.

Related Products