← Search results
CVE-LINKED INVENTORY51 SECURITY RECORDS
IBM Corporation
UrbanCode Deploy
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
This identity is present in BlackTree CVE records, but no product-specific publisher support or retirement history is currently registered in Lifecycle.
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-36162 | 2 Sep 2025 | UrbanCode Deploy: 8.1 ≤ 8.1.2.1 | IBM strongly suggests the following:; Upgrade affected versions to: 8.1.2.2 https://www.ibm.com/support/fixcentral/swg/downloadFixes or later | Update reference ↗ |
| CVE-2025-1998 | 27 Mar 2025 | 7.1 ≤ 7.1.2.21; 7.2 ≤ 7.2.3.14; 7.3 ≤ 7.3.2.9; 8.0 ≤ 8.0.1.4; 8.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-1997 | 27 Mar 2025 | 7.0 ≤ 7.0.5.25; 7.1 ≤ 7.1.2.21; 7.2 ≤ 7.2.3.14; 7.3 ≤ 7.3.2.9; 8.0 ≤ 8.0.1.4; 8.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-56469 | 27 Mar 2025 | 7.1 ≤ 7.1.2.22; 7.2 ≤ 7.2.3.15; 7.3 ≤ 7.3.2.10; 8.0 ≤ 8.0.1.5; 8.1 ≤ 8.1.0.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-55904 | 14 Feb 2025 | 7.0 ≤ 7.0.5.25; 7.1 ≤ 7.1.2.21; 7.2 ≤ 7.2.3.14; 7.3 ≤ 7.3.2.9; 8.0 ≤ 8.0.1.4; 8.1 ≤ 8.1.0.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-54176 | 8 Feb 2025 | 7.0 ≤ 7.0.5.25; 7.1 ≤ 7.1.2.21; 7.2 ≤ 7.2.3.14; 7.3 ≤ 7.3.2.9; 8.0 ≤ 8.0.1.4; 8.1 ≤ 8.1.0.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-45091 | 21 Jan 2025 | 7.0 ≤ 7.0.5.24; 7.1 ≤ 7.1.2.10; 7.2 ≤ 7.2.3.13 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-28781 | 10 May 2024 | 7.0 ≤ 7.0.5.20; 7.1 ≤ 7.1.2.16; 7.2 ≤ 7.2.3.9; 7.3 ≤ 7.3.2.4; 8.0 ≤ 8.0.0.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-22358 | 12 Apr 2024 | 7.0 ≤ 7.0.5.20; 7.1 ≤ 7.1.2.16; 7.2 ≤ 7.2.3.9; 7.3 ≤ 7.3.2.4; 8.0 ≤ 8.0.0.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-22339 | 12 Apr 2024 | 7.0 ≤ 7.0.5.20; 7.1 ≤ 7.1.2.16; 7.2 ≤ 7.2.3.9; 7.3 ≤ 7.3.2.4; 8.0 ≤ 8.0.0.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-22334 | 12 Apr 2024 | 7.0 ≤ 7.0.5.20; 7.1 ≤ 7.1.2.16; 7.2 ≤ 7.2.3.9; 7.3 ≤ 7.3.2.4; 8.0 ≤ 8.0.0.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-22359 | 12 Apr 2024 | 7.0 ≤ 7.0.5.20; 7.1 ≤ 7.1.2.16; 7.2 ≤ 7.2.3.9; 7.3 ≤ 7.3.2.4; 8.0 ≤ 8.0.0.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-22331 | 6 Feb 2024 | 7.0 ≤ 7.0.5.19; 7.1 ≤ 7.1.2.15; 7.2 ≤ 7.2.3.8; 7.3 ≤ 7.3.2.3; 8.0.0.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-47161 | 19 Dec 2023 | 7.2 ≤ 7.2.3.7; 7.3 ≤ 7.3.2.2; 7.1 ≤ 7.1.2.14 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-42012 | 19 Dec 2023 | 7.2 ≤ 7.2.3.7; 7.3 ≤ 7.3.2.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-42013 | 19 Dec 2023 | 7.1 ≤ 7.1.2.14; 7.2 ≤ 7.2.3.7; 7.3 ≤ 7.3.2.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-42015 | 19 Dec 2023 | 7.1 ≤ 7.1.2.14; 7.2 ≤ 7.2.3.7; 7.3 ≤ 7.3.2.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-40376 | 4 Oct 2023 | 7.1 ≤ 7.1.2.12; 7.2 ≤ 7.2.3.5; 7.3 ≤ 7.3.2.0 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-43877 | 6 May 2023 | 6.2 ≤ 6.2.7.19; 7.0 ≤ 7.0.5.14; 7.1 ≤ 7.1.2.10; 7.2 ≤ 7.2.3.3; 7.3 ≤ 7.3.0.1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-40751 | 17 Nov 2022 | 6.2.7.0 < 6.2.7.17; 7.0.0.0 < 7.0.5.12; 7.1.0.0 < 7.1.2.8; 7.2.0.0 < 7.2.3.1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-35716 | 31 Jul 2022 | 7.0.0.0; 7.1.0.0; 7.2.0.0; 6.2.0.0; 6.2.7.16; 7.0.5.11; 7.1.2.7; 7.2.3.0 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-22367 | 1 Jul 2022 | 6.2.7.15; 7.0.5.10; 7.1.2.6; 7.2.2.1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-22366 | 1 Jul 2022 | 6.2.7.15; 7.0.5.10; 7.1.2.6; 7.2.2.1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2021-39082 | 29 Apr 2022 | 7.0.5.2; 7.1.0.0; 7.1.1.0; 7.1.1.1; 7.1.1.2; 7.0.4.1; 7.0.4.2; 7.0.5.0 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-22315 | 27 Apr 2022 | 6.2.7.0; 7.0.3.0; 7.0.4.0; 7.1.0.0; 7.1.1.0; 7.1.1.2; 7.0.3.3; 7.0.4.2 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-22327 | 1 Apr 2022 | 7.0.5; 7.1.0; 7.1.1; 7.1.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2021-29711 | 8 Jul 2021 | 6.2.7.3; 7.0.3.0; 7.0.4.0; 7.1.0.0; 6.2.7.4; 6.2.7.8; 7.1.1.0; 6.2.7.9 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2020-4944 | 30 Mar 2021 | 7.0.3.0; 7.0.4.0; 7.1.0.0; 7.0.5.3; 7.1.1.0; 7.0.5.4; 7.1.1.1; 7.1.1.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-4884 | 30 Mar 2021 | 6.2.7.9; 7.0.5.4; 7.1.1.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-4848 | 30 Mar 2021 | 6.2.7.9; 7.0.5.4; 7.1.1.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-4484 | 6 Nov 2020 | 6.2.7.3; 7.0.3.0; 7.0.4.0; 6.2.7.4 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2020-4483 | 6 Nov 2020 | 6.2.7.3; 7.0.3.0; 7.0.4.0; 6.2.7.4 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2020-4482 | 6 Nov 2020 | 6.2.7.3; 7.0.3.0; 7.0.4.0; 6.2.7.4 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2020-4481 | 5 Aug 2020 | 6.2.7.3; 7.0.3.0; 7.0.4.0; 6.2.7.4 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-4667 | 11 May 2020 | 7.0.5.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-4202 | 23 Apr 2020 | 7.0.3.0; 7.0.4.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-4668 | 23 Apr 2020 | 7.0.4.0 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2020-4260 | 16 Apr 2020 | 7.0.5 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-4666 | 13 Feb 2020 | 7.0.3; 6.1.5 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2016-0373 | 30 Aug 2018 | 6.1.0.2; 6.0; 6.0.1; 6.0.1.1; 6.0.1.2; 6.0.1.3; 6.0.1.4; 6.0.1.5 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2017-1749 | 13 Aug 2018 | 6.1.0.2; 6.1; 6.1.0.1; 6.1.0.3; 6.1.0.4; 6.1.1; 6.1.1.1; 6.1.1.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-1752 | 25 May 2018 | 6.1.0.2; 6.1; 6.1.0.1; 6.1.0.3; 6.1.0.4; 6.1.1; 6.1.1.1; 6.1.1.2 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2017-1493 | 9 Jan 2018 | 6.1.0.2; 6.1; 6.1.0.1; 6.1.0.3; 6.1.0.4; 6.1.1; 6.1.1.1; 6.1.1.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-1149 | 25 Apr 2017 | 6.1.0.2, 6.0, 6.0.1, 6.0.1.1, 6.0.1.2, 6.0.1.3, 6.0.1.4, 6.0.1.5, 6.0.1.6, 6.1, 6.1.0.1, 6.1.0.3, 6.0.1.7, 6.0.1.8, 6.1.0.4, 6.1.1, 6.1.1.1, 6.1.1.2, 6.1.1.3, 6.1.1.4, 6.1.1.5, 6.0.1.9, 6.1.1.6, 6.1.1.7, 6.1.2, 6.0.1.10, 6.0.1.11, 6.1.1.8, 6.1.3, 6.1.3.1, 6.2, 6.2.0.1, 6.0.1.12, 6.1.3.2, 6.2.0.2, 6.2.1, 6.0.1.13, 6.2.1.1, 6.0.1.14, 6.1.3.3, 6.2.1.2, 6.2.2, 6.2.2.1, 6.2.3.0, 6.2.3.1, 6.1.3.4, 6.1.3.5 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2016-9006 | 8 Mar 2017 | 6.1.0.2; 6.0; 6.0.1; 6.0.1.1; 6.0.1.2; 6.0.1.3; 6.0.1.4; 6.0.1.5 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2016-9008 | 1 Feb 2017 | 6.1.0.2; 6.0; 6.0.1; 6.0.1.1; 6.0.1.2; 6.0.1.3; 6.0.1.4; 6.0.1.5 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2016-8938 | 1 Feb 2017 | 6.1.0.2; 6.0; 6.0.1; 6.0.1.1; 6.0.1.2; 6.0.1.3; 6.0.1.4; 6.0.1.5 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2016-6068 | 1 Feb 2017 | 6.1.0.2; 6.0; 6.0.1; 6.0.1.1; 6.0.1.2; 6.0.1.3; 6.0.1.4; 6.0.1.5 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2016-2942 | 1 Feb 2017 | 6.1.0.2; 6.0; 6.0.1; 6.0.1.1; 6.0.1.2; 6.0.1.3; 6.0.1.4; 6.0.1.5 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2016-2941 | 1 Feb 2017 | 6.1.0.2; 6.0; 6.0.1; 6.0.1.1; 6.0.1.2; 6.0.1.3; 6.0.1.4; 6.0.1.5 | 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.