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

IBM

Controller

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

Lifecycle evidence status

Official registry publication history is available at controller, but registry activity is not a publisher support boundary.

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-36421 18 Sep 2026 Controller: 11.0.0 ≤ 11.0.1 FP7, 11.1.0 ≤ 11.1.3 FP1 It is strongly recommended that you apply the most recent security updates:; Affected Product(s)Version(s)FixIBM Cognos Controller11.0.0 - 11.0.1 FP7 https://www.ibm.com/mysupport . Customers currently running IBM Controller 11.0 and 11.1 can upgrade to the 11.2 release stream at no additional charge. Update reference ↗
CVE-2025-36178 18 Sep 2026 Controller: 11.0.0 ≤ 11.0.1 FP7, 11.1.0 ≤ 11.1.3 FP1 It is strongly recommended that you apply the most recent security updates:; Affected Product(s)Version(s)FixIBM Cognos Controller11.0.0 - 11.0.1 FP7 https://www.ibm.com/mysupport . Customers currently running IBM Controller 11.0 and 11.1 can upgrade to the 11.2 release stream at no additional charge. Update reference ↗
CVE-2025-1350 18 Sep 2026 Controller: 11.0.0 ≤ 11.0.1 FP7, 11.1.0 ≤ 11.1.3 FP1 It is strongly recommended that you apply the most recent security updates:; Affected Product(s)Version(s)FixIBM Cognos Controller11.0.0 - 11.0.1 FP7 https://www.ibm.com/mysupport . Customers currently running IBM Controller 11.0 and 11.1 can upgrade to the 11.2 release stream at no additional charge. Update reference ↗
CVE-2026-5065 27 May 2026 11.0.1 ≤ 26.0.0.5; 11.1.0; 11.1.1; 11.1.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-36017 8 Dec 2025 11.1.0 ≤ 11.1.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-36102 8 Dec 2025 11.1.0 ≤ 11.1.1; 11.0.0 ≤ 11.0.1 FP6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-33111 8 Dec 2025 11.1.0 ≤ 11.1.1; 11.0.0 ≤ 11.0.1 FP6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-36015 8 Dec 2025 11.1.0 ≤ 11.1.1; 11.0.0 ≤ 11.0.1 FP6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-33079 27 May 2025 11.1.0; 11.0.0, 11.0.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-41778 1 Mar 2025 11.0.0 ≤ 11.0.1; 11.1.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-22363 7 Jan 2025 11.1.0; 11.0.0 ≤ 11.0.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-20455 7 Jan 2025 11.1.0; 11.0.0 ≤ 11.0.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-40702 7 Jan 2025 11.1.0; 11.0.0 ≤ 11.0.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-28778 7 Jan 2025 11.1.0; 11.0.0 ≤ 11.0.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-25037 7 Jan 2025 11.1.0; 11.0.0 ≤ 11.0.1 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.