← Search results
CVE-LINKED INVENTORY19 SECURITY RECORDS
IBM Corporation
TRIRIGA Application Platform
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-11372 | 22 Jun 2026 | 5.0.2 ≤ 5.0.3 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-4868 | 31 Jul 2023 | 3.0, 4.0, 4.4 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2022-43914 | 7 Apr 2023 | 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-2023-27876 | 7 Apr 2023 | 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-4277 | 17 Apr 2020 | 3.5.3; 3.6.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-4208 | 7 May 2019 | 3.5.3; 3.6.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-4207 | 7 May 2019 | 3.5.3; 3.6.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-2018-2008 | 7 May 2019 | 3.5.3; 3.6.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-2017-1465 | 7 Dec 2017 | 3.3; 3.3.1; 3.3.2; 3.4; 3.4.1; 3.4.2; 3.5; 3.5.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-1374 | 21 Jul 2017 | 3.3; 3.3.1; 3.3.2; 3.4; 3.4.1; 3.4.2; 3.5; 3.5.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-2017-1373 | 21 Jul 2017 | 3.3; 3.3.1; 3.3.2; 3.4; 3.4.1; 3.4.2; 3.5; 3.5.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-2017-1372 | 21 Jul 2017 | 3.3; 3.3.1; 3.3.2; 3.4; 3.4.1; 3.4.2; 3.5; 3.5.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-2017-1371 | 21 Jul 2017 | 3.3.2; 3.4; 3.4.1; 3.4.2; 3.5; 3.5.1; 3.5.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-1180 | 5 Apr 2017 | 3.3; 3.3.1; 3.3.2; 3.4; 3.4.1; 3.4.2; 3.5; 3.5.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-1171 | 31 Mar 2017 | 3.2; 3.2.1; 3.1; 3.0; 3.3; 3.3.1; 2.7; 2.6 | 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-1153 | 27 Mar 2017 | 3.2; 3.2.1; 3.1; 3.0; 3.3; 3.3.1; 3.3.2; 3.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-2016-9737 | 27 Mar 2017 | 3.2; 3.2.1; 3.1; 3.0; 3.3; 3.3.1; 3.3.2; 3.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-2016-6000 | 1 Feb 2017 | 3.2; 3.2.1; 3.1; 3.0; 3.3; 3.3.1; 2.7; 2.6 | 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-5980 | 1 Feb 2017 | 3.2; 3.2.1; 3.1; 3.0; 3.3; 3.3.1; 2.7; 2.6 | 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 ↗ |
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.