EOL.WikiEOL.Wiki
← ← Back to all products

BIG-IP

Active
Security & NetworkingLatest Version: 21.1.0Latest Release: May 5, 2026

F5 BIG-IP is an application delivery controller providing load balancing, security, and traffic management.

CISA known-exploited vulnerability signal

CISA KEV catalog version 2026.08.20 includes 3 manually mapped record(s) for this product.

Newest matching record added: Mar 27, 2026

Open the CISA KEV catalog ↗

This is a product-level catalog match, not a finding that the version shown above is vulnerable. Review each vendor advisory and affected-version range before acting.

Matching CVEs (showing up to 3)

  • CVE-2025-53521
  • CVE-2022-1388
  • CVE-2020-5902

Support summary

BIG-IP currently has supported cycles. Track the next EOL date and validate upgrades before your change window.

What do EOL and support statuses mean?

Next EOL

Mar 31, 2027

BIG-IP 17.1 · 222 days left

Supported cycles

3

5 lts

Versions

31

Latest Version

21.1.0

Active Support

3

EOL

28

Lifecycle Timeline

Today ↓
21.1
21.1
21.0
21.0
17.5
17.5
17.1
17.1
17.0
17.0
16.1
16.1
16.0
16.0
15.1
15.1
15.0
15.0
14.1
14.1
Active SupportSecurity SupportEOL

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
21.1May 5, 2026May 5, 2029May 5, 202921.1.0
Yes
Active
21.0Nov 6, 2025Aug 6, 2026Aug 6, 202621.0.0No
EOL
17.5Feb 27, 2025Jan 1, 2029Jan 1, 202917.5.1
Yes
Active
17.1Mar 14, 2023Mar 31, 2027Mar 31, 202717.1.3
Yes
Active
17.0Apr 26, 2022Jul 31, 2023Jul 31, 202317.0.0No
EOL
16.1Jul 7, 2021Jul 31, 2025Jul 31, 202516.1.6
Yes
EOL
16.0Jul 16, 2020Oct 7, 2021Oct 7, 202116.0.1.1No
EOL
15.1Dec 11, 2019Dec 31, 2024Dec 31, 202415.1.10
Yes
EOL
15.0May 23, 2019Aug 23, 2020Aug 23, 202015.0.1No
EOL
14.1Dec 11, 2018Dec 31, 2023Dec 31, 202314.1.5No
EOL
14.0Aug 9, 2018Nov 9, 2019Nov 9, 201914.0.1No
EOL
13.1Dec 19, 2017Dec 31, 2022Dec 31, 202313.1.5No
EOL
13.0Feb 22, 2017May 22, 2018May 22, 201913.0.1No
EOL
12.1May 18, 2016May 18, 2021May 18, 202212.1.6No
EOL
12.0Sep 2, 2015Dec 2, 2016Dec 2, 201712.0.0No
EOL
11.6Aug 25, 2014May 10, 2021May 10, 202211.6.5No
EOL
11.5Jan 31, 2014Apr 8, 2019Apr 8, 202011.5.10No
EOL
11.4Jun 11, 2013Sep 17, 2016Sep 17, 201711.4.1No
EOL
11.3Dec 17, 2012Dec 17, 2014Dec 17, 201511.3.0No
EOL
11.2Jun 11, 2012Dec 31, 2017Dec 31, 201811.2.1No
EOL
11.1Nov 28, 2011Nov 28, 2013Nov 28, 201411.1.0No
EOL
11.0Aug 24, 2011Aug 24, 2013Aug 24, 201411.0.0No
EOL
10.2May 4, 2010Dec 31, 2015Dec 31, 201610.2.4No
EOL
10.1Dec 17, 2009Mar 1, 2015Mar 1, 201610.1.0No
EOL
10.0Mar 12, 2009Aug 31, 2012Aug 31, 201310.0.1No
EOL
9.6Dec 20, 2007Mar 31, 2011Mar 31, 20129.6.1No
EOL
9.4Dec 20, 2006Aug 31, 2012Aug 31, 20139.4.8No
EOL
9.3Apr 27, 2006Mar 31, 2011Mar 31, 20129.3.1No
EOL
9.2Sep 29, 2005Jul 31, 2007Jul 31, 20089.2.5No
EOL
9.1Jul 26, 2005Apr 30, 2008Apr 30, 20099.1.3No
EOL
9.0Aug 23, 2004May 18, 2006May 18, 20079.0.5No
EOL

Data sources

Frequently Asked Questions

Which versions of BIG-IP have reached end of life?
The following BIG-IP versions have reached end of life and no longer receive security updates: 21.0, 17.0, 16.1, 16.0, 15.1, 15.0, 14.1, 14.0 (and 20 more). It is recommended to upgrade to a supported version.
Is it safe to continue using BIG-IP 21.0?
BIG-IP 21.0 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of BIG-IP?
The latest version of BIG-IP is 21.1.0, released in the 21.1 release cycle.
How many versions of BIG-IP are currently supported?
BIG-IP currently has 3 actively supported version(s): 21.1, 17.5, 17.1.
When does BIG-IP 21.1 reach end of life?
BIG-IP 21.1 is scheduled to reach end of life on May 5, 2029.
What should I do when BIG-IP reaches end of life?
When a BIG-IP version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.