IBM
Cloud Pak For Business Automation
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-11864 | 15 Sep 2026 | Cloud Pak for Business Automation: 26.0.0 ≤ 26.0.0 Interim Fix 001, 25.0.0 ≤ 25.0.0 Interim Fix 005, 24.0.1 ≤ 24.0.1 Interim Fix 008, 24.0.0 ≤ 24.0.0 Interim Fix 009 | IBM strongly recommends addressing the vulnerability now.; Affected Product(s)Version(s)Remediation / FixIBM Cloud Pak for Business AutomationV26.0.0 - V26.0.0-IF001Apply security fix 26.0.0-IF002 https://www.ibm.com/support/pages/readme-ibm-cloud-pak-business-automation-2600-if002 IBM Cloud Pak for Business AutomationV25.0.0 - V25.0.0-IF005Apply security fix 25.0.0-IF006 https://www.ibm.com/support/pages/readme-ibm-cloud-pak-business-automation-2500-if006 IBM Cloud Pak for Business AutomationV24.0.1 - V24.0.1-IF008Apply security fix 24.0.1-IF009 https://www.ibm.com/support/pages/readme-ibm-cloud-pak-business-automation-2401-if009 IBM Cloud Pak for Business AutomationV24.0.0 - V24.0.0-IF009Apply security fix 24.0.0-IF010 https://www.ibm.com/support/pages/readme-ibm-cloud-pak-business-automation-2400-if010; Any open source library may be included in one or more sub-components of IBM Cloud Pak for Business Automation. Open source updates are not always synchronized across all components. | Update reference ↗ |
| CVE-2026-12749 | 15 Sep 2026 | Cloud Pak for Business Automation: 26.0.0 ≤ 26.0.0 Interim Fix 001, 25.0.0 ≤ 25.0.0 Interim Fix 005, 24.0.1 ≤ 24.0.1 Interim Fix 008, 24.0.0 ≤ 24.0.0 Interim Fix 009 | IBM strongly recommends addressing the vulnerability now.; Affected Product(s)Version(s)Remediation / FixIBM Cloud Pak for Business AutomationV26.0.0 - V26.0.0-IF001Apply security fix 26.0.0-IF002 https://www.ibm.com/support/pages/readme-ibm-cloud-pak-business-automation-2600-if002 IBM Cloud Pak for Business AutomationV25.0.0 - V25.0.0-IF005Apply security fix 25.0.0-IF006 https://www.ibm.com/support/pages/readme-ibm-cloud-pak-business-automation-2500-if006 IBM Cloud Pak for Business AutomationV24.0.1 - V24.0.1-IF008Apply security fix 24.0.1-IF009 https://www.ibm.com/support/pages/readme-ibm-cloud-pak-business-automation-2401-if009 IBM Cloud Pak for Business AutomationV24.0.0 - V24.0.0-IF009Apply security fix 24.0.0-IF010 https://www.ibm.com/support/pages/readme-ibm-cloud-pak-business-automation-2400-if010; Any open source library may be included in one or more sub-components of IBM Cloud Pak for Business Automation. Open source updates are not always synchronized across all components. | Update reference ↗ |
| CVE-2026-12750 | 15 Sep 2026 | Cloud Pak for Business Automation: 26.0.0 ≤ 26.0.0 Interim Fix 001, 25.0.0 ≤ 25.0.0 Interim Fix 005, 24.0.1 ≤ 24.0.1 Interim Fix 008, 24.0.0 ≤ 24.0.0 Interim Fix 009 | IBM strongly recommends addressing the vulnerability now.; Affected Product(s)Version(s)Remediation / FixIBM Cloud Pak for Business AutomationV26.0.0 - V26.0.0-IF001Apply security fix 26.0.0-IF002 https://www.ibm.com/support/pages/readme-ibm-cloud-pak-business-automation-2600-if002 IBM Cloud Pak for Business AutomationV25.0.0 - V25.0.0-IF005Apply security fix 25.0.0-IF006 https://www.ibm.com/support/pages/readme-ibm-cloud-pak-business-automation-2500-if006 IBM Cloud Pak for Business AutomationV24.0.1 - V24.0.1-IF008Apply security fix 24.0.1-IF009 https://www.ibm.com/support/pages/readme-ibm-cloud-pak-business-automation-2401-if009 IBM Cloud Pak for Business AutomationV24.0.0 - V24.0.0-IF009Apply security fix 24.0.0-IF010 https://www.ibm.com/support/pages/readme-ibm-cloud-pak-business-automation-2400-if010; Any open source library may be included in one or more sub-components of IBM Cloud Pak for Business Automation. Open source updates are not always synchronized across all components. | Update reference ↗ |
| CVE-2026-12751 | 15 Sep 2026 | Cloud Pak for Business Automation: 26.0.0 ≤ 26.0.0 Interim Fix 001, 25.0.0 ≤ 25.0.0 Interim Fix 005, 24.0.1 ≤ 24.0.1 Interim Fix 008, 24.0.0 ≤ 24.0.0 Interim Fix 009 | IBM strongly recommends addressing the vulnerability now.; Affected Product(s)Version(s)Remediation / FixIBM Cloud Pak for Business AutomationV26.0.0 - V26.0.0-IF001Apply security fix 26.0.0-IF002 https://www.ibm.com/support/pages/readme-ibm-cloud-pak-business-automation-2600-if002 IBM Cloud Pak for Business AutomationV25.0.0 - V25.0.0-IF005Apply security fix 25.0.0-IF006 https://www.ibm.com/support/pages/readme-ibm-cloud-pak-business-automation-2500-if006 IBM Cloud Pak for Business AutomationV24.0.1 - V24.0.1-IF008Apply security fix 24.0.1-IF009 https://www.ibm.com/support/pages/readme-ibm-cloud-pak-business-automation-2401-if009 IBM Cloud Pak for Business AutomationV24.0.0 - V24.0.0-IF009Apply security fix 24.0.0-IF010 https://www.ibm.com/support/pages/readme-ibm-cloud-pak-business-automation-2400-if010; Any open source library may be included in one or more sub-components of IBM Cloud Pak for Business Automation. Open source updates are not always synchronized across all components. | Update reference ↗ |
| CVE-2026-12758 | 14 Sep 2026 | Cloud Pak for Business Automation: 26.0.0 ≤ 26.0.0 Interim Fix 001, 25.0.0 ≤ 25.0.0 Interim Fix 005, 24.0.1 ≤ 24.0.1 Interim Fix 008, 24.0.0 ≤ 24.0.0 Interim Fix 009 | IBM strongly recommends addressing the vulnerability now.; Affected Product(s)Version(s)Remediation / FixIBM Cloud Pak for Business AutomationV26.0.0 - V26.0.0-IF001Apply security fix 26.0.0-IF002 https://www.ibm.com/support/pages/readme-ibm-cloud-pak-business-automation-2600-if002 IBM Cloud Pak for Business AutomationV25.0.0 - V25.0.0-IF005Apply security fix 25.0.0-IF006 https://www.ibm.com/support/pages/readme-ibm-cloud-pak-business-automation-2500-if006 IBM Cloud Pak for Business AutomationV24.0.1 - V24.0.1-IF008Apply security fix 24.0.1-IF009 https://www.ibm.com/support/pages/readme-ibm-cloud-pak-business-automation-2401-if009 IBM Cloud Pak for Business AutomationV24.0.0 - V24.0.0-IF009Apply security fix 24.0.0-IF010 https://www.ibm.com/support/pages/readme-ibm-cloud-pak-business-automation-2400-if010; Any open source library may be included in one or more sub-components of IBM Cloud Pak for Business Automation. Open source updates are not always synchronized across all components. | Update reference ↗ |
| CVE-2026-12759 | 14 Sep 2026 | Cloud Pak for Business Automation: 26.0.0 ≤ 26.0.0 Interim Fix 001, 25.0.0 ≤ 25.0.0 Interim Fix 005, 24.0.1 ≤ 24.0.1 Interim Fix 008, 24.0.0 ≤ 24.0.0 Interim Fix 009 | IBM strongly recommends addressing the vulnerability now.; Affected Product(s)Version(s)Remediation / FixIBM Cloud Pak for Business AutomationV26.0.0 - V26.0.0-IF001Apply security fix 26.0.0-IF002 https://www.ibm.com/support/pages/readme-ibm-cloud-pak-business-automation-2600-if002 IBM Cloud Pak for Business AutomationV25.0.0 - V25.0.0-IF005Apply security fix 25.0.0-IF006 https://www.ibm.com/support/pages/readme-ibm-cloud-pak-business-automation-2500-if006 IBM Cloud Pak for Business AutomationV24.0.1 - V24.0.1-IF008Apply security fix 24.0.1-IF009 https://www.ibm.com/support/pages/readme-ibm-cloud-pak-business-automation-2401-if009 IBM Cloud Pak for Business AutomationV24.0.0 - V24.0.0-IF009Apply security fix 24.0.0-IF010 https://www.ibm.com/support/pages/readme-ibm-cloud-pak-business-automation-2400-if010; Any open source library may be included in one or more sub-components of IBM Cloud Pak for Business Automation. Open source updates are not always synchronized across all components. | Update reference ↗ |
| CVE-2026-81859 | 4 Sep 2026 | 26.0.0 ≤ 26.0.0 Interim Fix 001; 25.0.0 ≤ 25.0.0 Interim Fix 005; 24.0.1 ≤ 24.0.1 Interim Fix 008; 24.0.0 ≤ 24.0.0 Interim Fix 009 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-12762 | 5 Aug 2026 | 24.0.0; 24.0.1; 25.0.0; 26.0.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-36094 | 3 Feb 2026 | 25.0.0 ≤ 25.0.0 Interim Fix 002; 24.0.1 ≤ 24.0.1 Interim Fix 005; 24.0.0 ≤ 24.0.0 Interim Fix 007 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-36436 | 2 Feb 2026 | 25.0.0 ≤ 25.0.0 Interim Fix 002; 24.0.1 ≤ 24.0.1 Interim Fix 005; 24.0.0 ≤ 24.0.0 Interim Fix 007 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-36172 | 3 Nov 2025 | 25.0.0 ≤ 25.0.0 Interim Fix 001; 24.0.1 ≤ 24.0.1 Interim Fix 004; 24.0.0 ≤ 24.0.0 Interim Fix 006 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-36093 | 3 Nov 2025 | 25.0.0; 24.0.1; 24.0.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-36092 | 3 Nov 2025 | 25.0.0; 24.0.1; 24.0.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-36091 | 3 Nov 2025 | 25.0.0; 24.0.1; 24.0.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-36023 | 8 Aug 2025 | 24.0.0 ≤ 24.0.0 IF005; 24.0.1 ≤ 24.0.1 IF002 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-1838 | 3 May 2025 | 24.0.1 ≤ 24.0.1 IF001; 24.0.0 ≤ 24.0.0 IF004 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-41753 | 3 May 2025 | 24.0.0 ≤ 24.0.0 IF004; 24.0.1 ≤ 24.0.1 IF001 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-49348 | 5 Feb 2025 | 18.0.0, 18.0.1, 18.0.2, 19.0.1, 19.0.2, 19.0.3, 20.0.1, 20.0.2, 20.0.3, 21.0.1, 21.0.2, 21.0.3, 22.0.1, 22.0.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-52365 | 5 Feb 2025 | 18.0.0, 18.0.1, 18.0.2, 19.0.1, 19.0.2, 19.0.3, 20.0.1, 20.0.2, 20.0.3, 21.0.1, 21.0.2, 21.0.3, 22.0.1, 22.0.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-52364 | 5 Feb 2025 | 18.0.0, 18.0.1, 18.0.2, 19.0.1, 19.0.2, 19.0.3, 20.0.1, 20.0.2, 20.0.3, 21.0.1, 21.0.2, 21.0.3, 22.0.1, 22.0.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-37528 | 8 Jul 2024 | 18.0.0, 18.0.1, 18.0.2, 19.0.1, 19.0.2, 19.0.3, 20.0.1, 20.0.2, 20.0.3, 21.0.1, 21.0.2, 21.0.3, 22.0.1, 22.0.2, 23.0.1, 23.0.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-31897 | 8 Jul 2024 | 18.0.0, 18.0.1, 18.0.2, 19.0.1, 19.0.2, 19.0.3, 20.0.1, 20.0.2, 20.0.3, 21.0.1, 21.0.2, 21.0.3, 22.0.1, 22.0.2, 23.0.1, 23.0.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-50959 | 31 Mar 2024 | 18.0.0, 18.0.1, 18.0.2,19.0.1, 19.0.2, 19.0.3,20.0.1, 20.0.2, 20.0.3, 21.0.1, 21.0.2, 21.0.3, 22.0.1,2 2.0.2, 23.0.1, 23.0.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-40691 | 18 Dec 2023 | 18.0.0, 18.0.1, 18.0.2, 19.0.1, 19.0.2, 19.0.3, 20.0.1, 20.0.2, 20.0.3, 21.0.1, 21.0.2, 21.0.3, 22.0.1, 22.0.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-2023-35024 | 14 Oct 2023 | 18.0.0, 18.0.1, 18.0.2, 19.0.1, 19.0.2, 19.0.3, 20.0.1, 20.0.2, 20.0.3, 21.0.1, 21.0.2, 21.0.3, 22.0.1, 22.0.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-2023-22860 | 27 Feb 2023 | 18.0.0, 18.0.1, 18.0.2, 19.0.1, 19.0.2, 19.0.3, 20.0.1, 20.0.2, 20.0.3, 21.0.1, 21.0.2, 21.0.3, 22.0.1, 22.0.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-2023-23469 | 1 Feb 2023 | 18.0.0, 18.0.1,18.0.2,19.0.1,19.0.2,19.0.3,20.0.1,20.0.2,20.0.3,21.0.1,21.0.2,21.0.3,22.0.1,22.0.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2021-29859 | 2 May 2022 | 18.0.0; 18.0.1; 18.0.2; 19.0.1; 19.0.2; 19.0.3; 20.0.1; 20.0.2 | 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.