← Search results
CVE-LINKED INVENTORY60 SECURITY RECORDS
Ivanti
Connect Secure
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
This CVE identity is linked to the Lifecycle record Ivanti Connect Secure. 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
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2025-55144 | 9 Sep 2025 | See the vendor and CVE records for the affected range. | 22.7R2.9; 22.8R2; 22.7R1.6; 2.8R2.3-723; 22.8R1.4 (Fix deployed on 02-Aug-2025) | Update reference ↗ |
| CVE-2025-55143 | 9 Sep 2025 | See the vendor and CVE records for the affected range. | 22.7R2.9; 22.8R2; 22.7R1.6; 2.8R2.3-723; 22.8R1.4 (Fix deployed on 02-Aug-2025) | Update reference ↗ |
| CVE-2025-55142 | 9 Sep 2025 | See the vendor and CVE records for the affected range. | 22.7R2.9; 22.8R2; 22.7R1.6; 2.8R2.3-723; 22.8R1.4 (Fix deployed on 02-Aug-2025) | Update reference ↗ |
| CVE-2025-55141 | 9 Sep 2025 | See the vendor and CVE records for the affected range. | 22.7R2.9; 22.8R2; 22.7R1.6; 2.8R2.3-723; 22.8R1.4 (Fix deployed on 02-Aug-2025) | Update reference ↗ |
| CVE-2025-55139 | 9 Sep 2025 | See the vendor and CVE records for the affected range. | 22.7R2.9; 22.8R2; 22.7R1.6; 2.8R2.3-723; 22.8R1.4 (Fix deployed on 02-Aug-2025) | Update reference ↗ |
| CVE-2025-55148 | 9 Sep 2025 | See the vendor and CVE records for the affected range. | 22.7R2.9; 22.8R2; 22.7R1.6; 2.8R2.3-723; 22.8R1.4 (Fix deployed on 02-Aug-2025) | Update reference ↗ |
| CVE-2025-55147 | 9 Sep 2025 | See the vendor and CVE records for the affected range. | 22.7R2.9; 22.8R2; 22.7R1.6; 2.8R2.3-723; 22.8R1.4 (Fix deployed on 02-Aug-2025) | Update reference ↗ |
| CVE-2025-55146 | 9 Sep 2025 | See the vendor and CVE records for the affected range. | 22.7R2.9; 22.8R2; 22.7R1.6; 2.8R2.3-723; 22.8R1.4 (Fix deployed on 02-Aug-2025) | Update reference ↗ |
| CVE-2025-8711 | 9 Sep 2025 | See the vendor and CVE records for the affected range. | 22.7R2.9; 22.8R2; 22.7R1.6; 2.8R2.3-723; 22.8R1.4 (Fix deployed on 02-Aug-2025) | Update reference ↗ |
| CVE-2025-5468 | 12 Aug 2025 | See the vendor and CVE records for the affected range. | 22.7R2.8; 22.8R2; 22.7R1.5; 22.8R2.3-723; 22.8R1.4 (Fix deployed on 02-Aug-2025) | Update reference ↗ |
| CVE-2025-5466 | 12 Aug 2025 | See the vendor and CVE records for the affected range. | 22.7R2.8; 22.8R2; 22.7R1.5; 22.8R2.3-723; 22.8R1.4 (Fix deployed on 02-Aug-2025) | Update reference ↗ |
| CVE-2025-5462 | 12 Aug 2025 | See the vendor and CVE records for the affected range. | 22.7R2.8; 22.8R2; 22.7R1.5; 22.8R2.3-723; 22.8R1.4 (Fix deployed on 02-Aug-2025) | Update reference ↗ |
| CVE-2025-5456 | 12 Aug 2025 | See the vendor and CVE records for the affected range. | 22.7R2.8; 22.8R2; 22.7R1.5; 2.8R2.3-723; 22.8R1.4 (Fix deployed on 02-Aug-2025) | Update reference ↗ |
| CVE-2025-0292 | 8 Jul 2025 | See the vendor and CVE records for the affected range. | 22.7R2.8; 22.7R1.5 | Update reference ↗ |
| CVE-2025-0293 | 8 Jul 2025 | See the vendor and CVE records for the affected range. | 22.7R2.8; 22.7R1.5 | Update reference ↗ |
| CVE-2025-5464 | 8 Jul 2025 | See the vendor and CVE records for the affected range. | 22.7R2.8 | Update reference ↗ |
| CVE-2025-5463 | 8 Jul 2025 | See the vendor and CVE records for the affected range. | 22.7R2.8; 22.7R1.5 | Update reference ↗ |
| CVE-2025-5451 | 8 Jul 2025 | See the vendor and CVE records for the affected range. | 22.7R2.8; 22.7R1.5 | Update reference ↗ |
| CVE-2025-5450 | 8 Jul 2025 | See the vendor and CVE records for the affected range. | 22.7R2.8; 22.7R1.5 | Update reference ↗ |
| CVE-2024-38657 | 21 Feb 2025 | 22.7R2.4 < 22.7R2.4; 22.7R1.3 < 22.7R1.3 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-13843 | 11 Feb 2025 | See the vendor and CVE records for the affected range. | 22.7R2.6; 22.7R1.3 | Update reference ↗ |
| CVE-2024-13842 | 11 Feb 2025 | See the vendor and CVE records for the affected range. | 22.7R2.3; 22.7R1.3 | Update reference ↗ |
| CVE-2024-13830 | 11 Feb 2025 | See the vendor and CVE records for the affected range. | 22.7R2.6; 22.7R1.3 | Update reference ↗ |
| CVE-2024-12058 | 11 Feb 2025 | See the vendor and CVE records for the affected range. | 22.7R2.6; 22.7R1.3 | Update reference ↗ |
| CVE-2024-10644 | 11 Feb 2025 | See the vendor and CVE records for the affected range. | 22.7R2.4; 22.7R1.3 | Update reference ↗ |
| CVE-2025-22467 | 11 Feb 2025 | See the vendor and CVE records for the affected range. | 22.7R2.6 | Update reference ↗ |
| CVE-2025-0283 | 8 Jan 2025 | 22.7R1.2 | 22.7R2.5 | Update reference ↗ |
| CVE-2024-37401 | 11 Dec 2024 | 22.7R2.1 < 22.7R2.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-37377 | 11 Dec 2024 | 22.7R2.3 < 22.7R2.3 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-11634 | 10 Dec 2024 | See the vendor and CVE records for the affected range. | 22.7R2.3; 22.7R1.2 | Update reference ↗ |
| CVE-2024-11633 | 10 Dec 2024 | See the vendor and CVE records for the affected range. | 22.7R2.4 | Update reference ↗ |
| CVE-2024-9844 | 10 Dec 2024 | See the vendor and CVE records for the affected range. | 22.7R2.4 | Update reference ↗ |
| CVE-2024-38655 | 13 Nov 2024 | 22.7R2.1 < 22.7R2.1; 9.1R18.9 < 9.1R18.9; 22.7R1.1 < 22.7R1.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-39712 | 13 Nov 2024 | 22.7R2.1 < 22.7R2.1; 9.1R18.7 < 9.1R18.7; 22.7R1.1 < 22.7R1.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-37400 | 13 Nov 2024 | 22.7R2.3 < 22.7R2.3 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-38649 | 13 Nov 2024 | 22.7R2.1 < 22.7R2.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-39711 | 13 Nov 2024 | 22.7R2.1 < 22.7R2.1; 9.1R18.7 < 9.1R18.7; 22.7R1.1 < 22.7R1.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-39709 | 13 Nov 2024 | 22.6R2 < 22.6R2; 22.7R1 < 22.7R1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-38656 | 13 Nov 2024 | 22.7R2.2 < 22.7R2.2; 9.1R18.9 < 9.1R18.9; 22.7R1.2 < 22.7R1.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-39710 | 13 Nov 2024 | 22.7R2.1 < 22.7R2.1; 9.1R18.7 < 9.1R18.7; 22.7R1.1 < 22.7R1.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-11004 | 12 Nov 2024 | See the vendor and CVE records for the affected range. | 22.7R2.1; 22.7R1.1 | Update reference ↗ |
| CVE-2024-11005 | 12 Nov 2024 | See the vendor and CVE records for the affected range. | 22.7R2.1; 22.7R1.1 | Update reference ↗ |
| CVE-2024-11006 | 12 Nov 2024 | See the vendor and CVE records for the affected range. | 22.7R2.1; 22.7R1.1 | Update reference ↗ |
| CVE-2024-11007 | 12 Nov 2024 | See the vendor and CVE records for the affected range. | 22.7R2.1; 22.7R1.1 | Update reference ↗ |
| CVE-2024-8495 | 12 Nov 2024 | See the vendor and CVE records for the affected range. | 22.7R2.1; 22.7R1.1 | Update reference ↗ |
| CVE-2024-47909 | 12 Nov 2024 | See the vendor and CVE records for the affected range. | 22.7R2.3; 22.7R1.2 | Update reference ↗ |
| CVE-2024-47907 | 12 Nov 2024 | See the vendor and CVE records for the affected range. | 22.7R2.3 | Update reference ↗ |
| CVE-2024-47906 | 12 Nov 2024 | 22.4R2 ≤ 22.7R2.2 | 22.7R2.3; 22.7R1.2 | Update reference ↗ |
| CVE-2024-9420 | 12 Nov 2024 | See the vendor and CVE records for the affected range. | 22.7R2.3; 22.7R1.2 | Update reference ↗ |
| CVE-2024-47905 | 12 Nov 2024 | See the vendor and CVE records for the affected range. | 22.7R2.3; 22.7R1.2 | Update reference ↗ |
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.