Evidence-linked product lifecycle intelligenceSUPPORT · SECURITY · RETIREMENT
← Search results
CVE-LINKED INVENTORY255 SECURITY RECORDS

F5

BIG-IP

Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.

Lifecycle evidence status

This CVE identity is linked to the Lifecycle record BIG-IP. Use that record for publisher support phases and retirement dates.

A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.

CVE-observed version history

CVEPublishedAffected versionsFixed version informationPublisher evidence
CVE-2025-22846 5 Feb 2025 17.1.0 < 17.1.2; 16.1.0 < 16.1.5; 15.1.0 < *; 1.8.0 < 1.9.1; 1.7.0 < 1.7.7 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-23412 5 Feb 2025 17.1.0 < 17.1.2; 16.1.3 < 16.1.5 15.1.0 < * Update reference ↗
CVE-2025-23239 5 Feb 2025 17.1.1 < 17.1.2 16.1.0 < *; 15.1.0 < * Update reference ↗
CVE-2025-24326 5 Feb 2025 17.1.0 < 17.1.2; 16.1.0 < 16.1.5; 15.1.0 < * No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-20045 5 Feb 2025 17.1.0 < 17.1.2; 16.1.0 < 16.1.5; 15.1.0 < * No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-22891 5 Feb 2025 17.1.0 < 17.1.2; 16.1.0 < 16.1.5; 15.1.0 < * No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-20058 5 Feb 2025 17.1.0 < 17.1.2; 16.1.0 < *; 15.1.0 < * No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-23415 5 Feb 2025 17.1.0 < 17.1.2; 16.1.0 < 16.1.5; 15.1.0 < * No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-21091 5 Feb 2025 17.1.0 < 17.1.2; 16.1.0 < *; 15.1.0 < * No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-21087 5 Feb 2025 17.1.0 < 17.1.2; 16.1.0 < *; 15.1.0 < *; 20.0.0 < 20.1.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-45844 16 Oct 2024 17.1.0 < 17.1.1.4; 16.1.0 < 16.1.5; 15.1.0 < 15.1.10.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-41727 14 Aug 2024 16.1.0 < 16.1.5; 15.1.0 < * 17.1.0 < * Update reference ↗
CVE-2024-41164 14 Aug 2024 17.1.0 < 17.1.1; 16.1.0 < 16.1.5; 15.1.0 < 15.1.10; 1.1.0 < 1.2.0; 1.5.0 < 1.9.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-39778 14 Aug 2024 17.1.0 < 17.1.1; 16.1.0 < 16.1.5; 15.1.0 < * No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-41723 14 Aug 2024 17.1.0 < 17.1.1; 16.1.0 < 16.1.5; 15.1.0 < * No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-32761 8 May 2024 15.1.0 < 15.1.10 17.1.0 < *; 16.1.0 < * Update reference ↗
CVE-2024-31156 8 May 2024 17.1.0 < 17.1.1.3; 16.1.0 < 16.1.4.3; 15.1.0 < 15.1.10.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-33604 8 May 2024 17.1.0 < 17.1.1.3; 16.1.0 < 16.1.4.3; 15.1.0 < 15.1.10.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-28889 8 May 2024 17.1.0 < 17.1.1.3; 16.1.2.1 < 16.1.4.3; 15.1.5 < 15.1.10.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-27202 8 May 2024 17.1.0 < 17.1.1.3; 16.1.0 < 16.1.4.3; 15.1.0 < 15.1.10.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-25560 8 May 2024 17.1.0 < 17.1.1; 16.1.0 < 16.1.4; 15.1.0 < *; 1.1.0 < 1.2.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-33608 8 May 2024 17.1.0 < 17.1.1 16.1.0 < *; 15.1.0 < * Update reference ↗
CVE-2024-23982 14 Feb 2024 See the vendor and CVE records for the affected range. 17.0.0 < *; 16.1.0 < *; 15.1.0 < * Update reference ↗
CVE-2024-21763 14 Feb 2024 17.1.0 < 17.1.1; 16.1.0 < 16.1.4; 15.1.0 < 15.1.10 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-23805 14 Feb 2024 17.1.0 < 17.1.1; 16.1.0 < 16.1.4; 15.1.0 < 15.1.10 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-21789 14 Feb 2024 17.1.0 < 17.1.1 16.1.0 < *; 15.1.0 < * Update reference ↗
CVE-2024-23308 14 Feb 2024 17.1.0 < 17.1.1 16.1.0 < *; 15.1.0 < * Update reference ↗
CVE-2024-23603 14 Feb 2024 17.1.0 < 17.1.1; 16.1.0 < 16.1.4; 15.1.0 < 15.1.10 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-24775 14 Feb 2024 17.1.0 < 17.1.1; 16.1.0 < 16.1.4; 15.1.0 < 15.1.10 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-23314 14 Feb 2024 17.1.0 < 17.1.1; 16.1.0 < 16.1.4; 15.1.0 < 15.1.9; 1.5.0 < 1.8.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-22093 14 Feb 2024 17.1.0 < 17.1.1; 16.1.0 < 16.1.4; 15.1.0 < 15.1.9 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-23979 14 Feb 2024 17.1.0 < 17.1.1; 16.1.0 < 16.1.4; 15.1.0 < 15.1.9 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-21849 14 Feb 2024 16.1.0 < 16.1.4 17.1.0 < *; 15.1.0 < * Update reference ↗
CVE-2024-21771 14 Feb 2024 17.1.0 < 17.1.1; 16.1.0 < 16.1.4; 15.1.0 < 15.1.9 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-21782 14 Feb 2024 17.1.0 < 17.1.1; 16.1.0 < 16.1.4; 15.1.0 < 15.1.9; 8.0.0 < * No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-23976 14 Feb 2024 17.1.0 < 17.1.1; 16.1.0 < 16.1.4; 15.1.0 < 15.1.9 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-22389 14 Feb 2024 17.1.0 < 17.1.1; 16.1.0 < 16.1.4; 15.1.0 < 15.1.9 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-45219 10 Oct 2023 16.1.0 < 16.1.4; 15.1.0 < 15.1.9; 14.1.0 < *; 13.1.0 < * 17.1.0 < * Update reference ↗
CVE-2023-43746 10 Oct 2023 16.1.0 < 16.1.4; 15.1.0 < 15.1.9; 14.1.0 < *; 13.1.0 < * 17.1.0 < * Update reference ↗
CVE-2023-43485 10 Oct 2023 16.1.0 < 16.1.4; 15.1.0 < 15.1.9; 14.1.0 < *; 13.1.0 < *; 8.1.0 < *; 8.2.0 < 8.2.0.1.0.13.97-ENG; 8.3.0 < 8.3.0.0.12.118-ENG 17.1.0 < * Update reference ↗
CVE-2023-42768 10 Oct 2023 16.1.0 < 16.1.4; 15.1.0 < 15.1.9; 14.1.0 < *; 13.1.0 < * 17.1.0 < * Update reference ↗
CVE-2023-41964 10 Oct 2023 16.1.0 < 16.1.4; 15.1.0 < 15.1.9; 14.1.0 < *; 13.1.0 < *; 8.1.0 < *; 8.2.0 < 8.2.0.1.0.13.97-ENG; 8.3.0 < 8.3.0.0.12.118-ENG 17.1.0 < * Update reference ↗
CVE-2023-41373 10 Oct 2023 17.1.0 < 17.1.0.3; 16.1.0 < 16.1.4.1; 15.1.0 < 15.1.10.2; 14.1.0 < 14.1.5.6; 13.1.0 < * No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-41253 10 Oct 2023 16.1.0 < 16.1.4; 15.1.0 < 15.1.9; 14.1.0 < *; 13.1.0 < * 17.1.0 < * Update reference ↗
CVE-2023-41085 10 Oct 2023 16.1.0 < 16.1.4; 15.1.0 < 15.1.9; 14.1.0 < *; 13.1.0 < * 17.1.0 < * Update reference ↗
CVE-2023-40542 10 Oct 2023 16.1.0 < 16.1.4; 15.1.0 < 15.1.9; 14.1.0 < *; 13.1.0 < * 17.1.0 < * Update reference ↗
CVE-2023-40537 10 Oct 2023 16.1.0 < 16.1.4; 15.1.0 < 15.1.9; 14.1.0 < *; 13.1.0 < * 17.1.0 < * Update reference ↗
CVE-2023-40534 10 Oct 2023 17.1.0 < 17.1.0.3.0.23.4-ENG; 16.1.0 < 16.1.4.1.0.13.5-ENG; 1.6.0 < * 15.1.0 < *; 14.1.0 < *; 13.1.0 < * Update reference ↗
CVE-2023-39447 10 Oct 2023 16.1.0 < 16.1.4; 15.1.0 < 15.1.8; 6.0 < 9.0 17.1.0 < *; 14.1.0 < *; 13.1.0 < * Update reference ↗
CVE-2023-38423 2 Aug 2023 17.1.0 < 17.1.0.2; 16.1.0 < 16.1.3.5; 15.1.0 < 15.1.9.1; 14.1.0 < 14.1.5.5; 13.1.0 < * No fixed version is explicitly recorded in the structured CVE data. Use CVE record

How this record is maintained

The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.