← Search results
CVE-LINKED INVENTORY26 SECURITY RECORDS
IBM
Planning Analytics
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-2026-13365 | 13 Aug 2026 | 2.0; 2.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-42017 | 22 Dec 2023 | 2.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2022-22339 | 8 Apr 2022 | 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-22308 | 21 Feb 2022 | 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-2021-38873 | 24 Nov 2021 | 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-2021-20526 | 27 Oct 2021 | 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-2021-20580 | 29 Jun 2021 | 2.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2021-20477 | 29 Jun 2021 | 2.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-4562 | 26 Apr 2021 | 2.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-4882 | 22 Mar 2021 | 2.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-4953 | 23 Feb 2021 | 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-2020-4881 | 19 Jan 2021 | 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-2020-4873 | 19 Jan 2021 | 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-2020-4871 | 19 Jan 2021 | 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-2020-4764 | 18 Dec 2020 | 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-2020-4653 | 19 Aug 2020 | 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-2020-4648 | 19 Aug 2020 | 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-2020-4645 | 29 Jul 2020 | 2.0.0; 2.0.9.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-2020-4644 | 29 Jul 2020 | 2.0.0; 2.0.9.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-2020-4527 | 20 Jul 2020 | 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-2020-4361 | 20 Jul 2020 | 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-2019-4613 | 5 Feb 2020 | 2.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-4716 | 18 Dec 2019 | Planning Analytics: 2.0.0, 2.0.8 | 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-2019-4612 | 9 Dec 2019 | 2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-4611 | 9 Dec 2019 | 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-2018-1933 | 1 May 2019 | 2.0.3; 2.0; 2.0.1; 2.0.2; 2.0.4; 2.0.5; 2.0.6 | 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.