Juniper MX and M Series (hardware) M160 · Version Status
Juniper MX and M Series (hardware) M160 End of Life Date
Juniper MX and M Series (hardware) M160 end-of-life date, support status, and CVE risk. Dates read at the vendor's own lifecycle pages (support.juniper.net); the source of each date is on the product page.
⚠
Juniper MX and M Series (hardware) M160 is past end of life. This version no longer receives security patches. 5551 days past EOL — migrate to a supported version immediately.
EOL Date
Jul 31, 2011
5551 days past EOL
Latest Release
M160 platform
Standard release
Release Date
—
Juniper MX and M Series (hardware) M160 series
Lifecycle detail
It has been without security patches for 15 years and 3 months.
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build.
Methodology → ·
View score card →
Extended Support
Extended Juniper MX and M Series (hardware) M160 support is available
Commercial vendors offer security patches beyond EOL. Compare your options.
Compare Options →
All Juniper MX and M Series (hardware) Versions
| Version | Latest | EOL Date | Status |
|---|
| M40 |
M40 router base system |
Sep 30, 2008 |
EOL |
| M10 |
M5 and M10 products |
Jan 31, 2010 |
EOL |
| M5 |
M5 and M10 products |
Jan 31, 2010 |
EOL |
| → M160 |
M160 platform |
Jul 31, 2011 |
EOL |
| M20 |
M20 platform |
Dec 31, 2012 |
EOL |
| M40e |
M40e Platform |
Jan 31, 2016 |
EOL |
| M320 |
M320BASE, M320BASE-AC/DC, M320BASE-EC(-AC/-DC), CHAS-BP-M320-S, CIP-M320-S, CRAFT-M320-S, M320-FPC1/2/3-E3 |
Dec 31, 2022 |
EOL |
| M120 |
M120BASE-AC, M120BASE-DC, CHAS-MP-M120-S, CB-M120-S, CRAFT-M120-S, FEB-M120, M120-FPC1/2/3, M120-CFPC-* |
Dec 31, 2022 |
EOL |
What does Juniper MX and M Series (hardware) M160 end of life mean?
When Juniper MX and M Series (hardware) M160 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.
The CVE blind spot: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running Juniper MX and M Series (hardware) M160 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to Juniper MX and M Series (hardware) MX240 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Juniper MX and M Series (hardware) M160 reach end of life?
Juniper MX and M Series (hardware) M160 reached end of life on July 31, 2011. This version is no longer receiving security patches.
Is Juniper MX and M Series (hardware) M160 still supported?
No. Juniper MX and M Series (hardware) M160 reached end of life on July 31, 2011 and is no longer receiving security patches.
What should I upgrade to from Juniper MX and M Series (hardware) M160?
The recommended upgrade from Juniper MX and M Series (hardware) M160 is
Juniper MX and M Series (hardware) MX240 — the latest actively supported version. Check the
Juniper MX and M Series (hardware) full timeline for all supported versions.
What are the security risks of running Juniper MX and M Series (hardware) M160 past EOL?
When Juniper MX and M Series (hardware) M160 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL Juniper MX and M Series (hardware) should migrate immediately or implement compensating controls.