IBM Support

Readme for IBM Cloud Pak for Business Automation 24.0.1 IF007

Fix Readme


Abstract

The following document is for IBM Cloud Pak for Business Automation 24.0.1 IF007. It includes the CASE package download, installation information, and the list of APARs/Known Issues that are resolved in this interim fix.

Content

Readme file for:IBM Cloud Pak® for Business Automation
Product Release:24.0.1
Update Name:24.0.1 IF007
Fix ID:24.0.1-WS-CP4BA-IF007
Publication Date:26 March 2026
 

Before installation

  1. Ensure you take regular backups of any databases associated with the environment.
  2. Ensure your operators are in a healthy state, before upgrading. 
    If one or more operators are failing, then it can prevent the system from completing an upgrade.
    It is recommended to check a few of the important CR statuses to ensure there are not failures and the statuses appear ready for the various installed components. Check the status of the following CRs when they exist:
  3. oc get icp4acluster -o yaml 
oc get content -o yaml
oc get Foundation -o yaml
  4. Remove any image settings in CRs
    If you used any individual image tag settings in your CRs, it could prevent the operator from updating the images to the appropriate version. Ensure you remove any of these settings when you upgrade. This doesn't apply to starter installation as it requires a new install.
 

Installing the interim fix

 
This interim fix contains the following version of Cloud Pak for Business Automation and Cloud Pak Foundational Services (CPFS):
  • Cloud Pak for Business Automation 24.0.1-IF007
  • Cloud Pak Foundational Services 4.17
Note:  This interim fix only supports the Cloud Pak Foundational Services listed above. It is important that you deploy or upgrade Cloud Pak for Business Automation using the catalog sources in this readme document.  If you have other Cloud Paks installed on the same OCP cluster, be sure to check the compatibility of the Cloud Pak Foundational Services versions listed above with other Cloud Paks' specifications.
 
 
Cloud Pak for Business Automation (CP4BA) 24.0.1 interim fixes are released to the v24.1 operator channel. Once the operators are upgraded, it triggers rolling updates for all the pods it manages to ensure they are updated to the appropriate version to match the operator.
 
NOTE :
  • If you have freshly deployed Automation Document Processing as a part of your CP4BA deployment and the deployment is configured with a Microsoft Active Directory ( MSAD) LDAP or IBM Security Directory Server ( SDS / TDS) LDAP follow the steps for Business Teams Service , you must follow the post upgrade steps listed in Completing the IBM Automation Document Processing upgrade after upgrading to this 24.0.1 interim fix
  • Starting with this interim fix, Java 17 or a version newer is required and must be installed on the bastion host where the deployment scripts are executed before running either a fresh installation or an upgrade to this iFix. Users can specify a custom Java installation directory using the flag --java-path while executing the cp4a-deployment.sh script or cp4a-prerequisites.sh script.
 
 
Step 1: Download the installation and upgrade scripts

  1. Download the 24.0.1 IF007 branch by using the following git clone command.

    git clone -b 24.0.1-IF007 https://github.com/icp4a/cert-kubernetes.git
 
Step 2:  Perform an online/offline fresh installation or an upgrade on an existing online/offline deployment.
 
Depending on the current setup and state of your existing environment, there are various actions that need to be taken. The following scenarios cover what actions might be needed for a particular setup.
 

For an upgrade scenario, these are the Cloud Pak foundational services migration modes supported -

Migration Mode Support
Cluster-scoped to Namespace-scopedSupported (This is the recommended approach if your current deployment is using cluster-scoped CPFs)
Namespace-scoped to Namespace-scopedSupported (If your CPFs deployment is already namespace-scoped, then continue to remain at namespace-scoped)
Cluster-scoped to Cluster-scoped Not Supported (Please follow the recommended upgrade from Cluster-scoped to Namespace-scoped for CPFs)
Cluster-scoped ("All namespaces") to Cluster-scoped ("All namespaces")Supported  ( There is no migration path from Cluster-scoped ("All namespaces") to Namespace-scoped )


Note: The recommended migration mode for an instance with cluster scoped Cloud Pak foundational services is to namespace scoped Cloud Pak foundational services.

 
  • Scenario 1: You are installing a Starter deployment online or have an existing online Starter deployment
    Warning: If you have an existing Cloud Pak Foundation Services instance installed at the cluster scoped level or in the namespace where CP4BA is being installed, then it is not supported. The Starter deployment of CP4BA is only supported when deploying into a new namespace without CPFs.
    Actions: Starter deployments do not support upgrades; however, you can use this interim fix content to perform a Starter deployment. To deploy a Starter deployment using the content of this interim fix, please see install a new Starter environment and use the installation scripts from the branch that you cloned above.
  • Scenario 2: You are installing online Production deployment
    Warning: If you have an existing Cloud Pak Foundation Services instance installed at the cluster scoped level or in the namespace where CP4BA is being installed, then it is not supported. The Production deployment of CP4BA is only supported when deploying into a new namespace without CPFs.
    Actions: To deploy an online Production deployment without using a local registry, please follow steps in install a new online Production environment and use the installation scripts from the branch that you cloned above.
  • Scenario 3: You are installing offline/airgap Production deployment
    Warning: If you have an existing Cloud Pak Foundation Services instance installed at the cluster scoped level or in the namespace where CP4BA is being installed, then it is not supported. The Production deployment of CP4BA is only supported when deploying into a new namespace without CPFs.
    Note: As prerequisites for this scenario, you must follow steps here to set up the bastion host to mirror images to the registry and further to set up the private registry. The mirroring of images can be completed using "oc mirror" for the mirroring images process. If you are looking to install only a set of capabilities then you can make use of filters listed in Table 1 so that you can only download the specific set of images that you require. Please note that if the set of capabilities includes Business Automation Workflow, Process Federation Server, Workflow Process Service or Business Automation Insights make sure to include the filter "ibm_es_1_1_2667".
    Actions:

    1. To deploy an airgap/offline Production deployment, find mirror file cp4ba-case-to-be-mirrored-24.0.1-IF007.txt for this interim fix from the branch that you cloned above under the scripts/airgap directory. Execute this command from your bastion host to download the CASE files.

      oc ibm-pak get -c file://(absolute path to file)/cp4ba-case-to-be-mirrored-24.0.1-IF007.txt

      The absolute path to file needs to be a path starting from "/". For example, "/opt".

    2. You will need to mirror the images associated with the new cp4ba-case-to-be-mirrored-24.0.1-IF007.txt mirror file. 

      export CASE_NAME=ibm-cp-automation
export CASE_VERSION=24.1.7
export CASE_INVENTORY_SETUP=cp4aOperatorSetup
export TARGET_REGISTRY=<target-registry>
export NAMESPACE=<cp4ba_namespace_name>

      Follow the instructions for either mirroring option in Mirroring images to the private registry using the new CASE version associated with this interim fix.

    3. Login to the cluster and go to namespace for the operator from the bastion host.

      oc login https://<CLUSTERIP>:<port> -u <ADMINISTRATOR>
oc project ${NAMESPACE}
    4. From your bastion host, install the catalog sources and operators using the steps listed in Install Catalog Source and Operators using cluster admin script.
    5. Follow the remaining steps from Question 6 listed here to complete the installations of offline/airgap Production deployment.

  • Scenario 4: Your installed Production deployment version is 21.0.3 IF031 or newer (If you do not have 21.0.3 IF031 or newer, you need to upgrade to 21.0.3 IF031 or newer before proceeding with this upgrade).
    Note: Direct upgrade from 21.0.3 IF031 or newer to this interim fix is not supported.  For this scenario, complete an upgrade to 24.0.0 GA or any of the newer 24.0.0 interim fixes, and then perform an upgrade from the 24.0.0 interim fix to this current interim fix.

    Actions:  

    1. Complete a direct upgrade to 24.0.0 GA or a newer 24.0.0 interim fix.
    2. Complete an upgrade from 24.0.0 GA or a newer 24.0.0 interim fix to the current 24.0.1 interim fix.
      • For online upgrade, follow the instructions listed in Scenario 7.
      • For offline upgrade, follow the instructions listed in Scenario 8.

     

  • Scenario 5: Your installed Production deployment version is 22.0.2 IF006(If you do not have 22.0.2 IF006, you need to upgrade to 22.0.2 IF006 before proceeding with this upgrade).
    Note: Direct upgrade from 22.0.2 IF006 to this interim fix is not supported.  For this scenario, complete an upgrade to 24.0.0 GA first or a newer 24.0.0 interim fix, and then perform an upgrade to this current interim fix.
    Actions:  

    1. Complete a direct upgrade to 24.0.0 GA or a newer 24.0.0 interim fix.
    2. Complete an upgrade from 24.0.0 GA or a newer 24.0.0 interim fix to the current 24.0.1 interim fix.
      • For online upgrade, follow the instructions listed in Scenario 7.
      • For offline upgrade, follow the instructions listed in Scenario 8.

     

  • Scenario 6: Your installed Production deployment version is 23.0.2 IF006 (If you do not have 23.0.2 IF006 you need to upgrade to 23.0.2 IF006 before proceeding with this upgrade).
    Note: Direct upgrade from 23.0.2 IF006 to this interim fix is not supported.  For this scenario, complete an upgrade to 24.0.0 GA first or a newer 24.0.0 interim fix, and then perform an upgrade to this current interim fix.
    Actions:
    1. Complete a direct upgrade to 24.0.0 GA or a newer 24.0.0 interim fix.
    2. Complete an upgrade from 24.0.0 GA or a newer 24.0.0 interim fix to the current 24.0.1 interim fix.
      • For online upgrade, follow the instructions listed in Scenario 7.
      • For offline upgrade, follow the instructions listed in Scenario 8.
  • Scenario 7: Your installed Production deployment version is 24.0.0 GA or newer.

    Warning:
    All instructions to download the installation and upgrade scripts in the Knowledge Center links referenced below can be ignored. Instead use the installation and upgrade scripts downloaded in Step 1
    Actions:
    For online upgrade, follow the upgrade instructions documented in Upgrading CP4BA multi-pattern clusters from 24.0.0 in online environment.
    For offline upgrade, you must first complete the prerequisites by following steps here to set up the bastion host to mirror images to the registry and further to set up the private registry. The mirroring of images can be completed using "oc mirror" for the mirroring images process manually  or using"oc mirror" for the mirroring images process by script . Once the mirroring of images is completed, follow the upgrade instructions documented in Upgrading CP4BA multi-pattern clusters from 24.0.0 in online environment.

  • Scenario 8:  Your installed Production deployment is 24.0.1 GA or newer.

    Note:
    For a dedicated deployment or namespace scoped deployment, the value for < CP4BA Namespace >  should be the namespace where all IBM Cloud Pak foundational services/CP4BA Operators and Services are deployed. If the CP4BA Operators and Services are deployed in different namespaces( separation of duties), the value for < CP4BA Namespace > should be the namespace where all IBM Cloud Pak foundational services/CP4BA Operators are deployed in.
    Warning:
    For a CP4BA Deployment with BAI ( Business Automation Insights ) selected as an optional component, it is recommended to create BAI savepoints before starting the upgrade process to this interim fix. For Flink event processing to resume from its previous state, savepoints are required to be created before the upgrade and specified in the updated CR. BAI savepoints can be created by following the below steps.

    •  Retrieve the name of the InsightsEngine custom resource file.

      InsightsEngine_CR=$(kubectl get InsightsEngine --no-headers --ignore-not-found -n <CP4BA-Namespace> -o name)
      Retrieve and export the below details.
      export MANAGEMENT_URL=$(kubectl get ${InsightsEngine_CR} --no-headers --ignore-not-found -n <CP4BA Namespace> -o jsonpath='{.status.components.management.endpoints[?(@.scope=="External")].uri}')
export MANAGEMENT_AUTH_SECRET=$(kubectl get ${InsightsEngine_CR} --no-headers --ignore-not-found -n <CP4BA Namespace> -o jsonpath='{.status.components.management.endpoints[?(@.scope=="External")].authentication.secret.secretName}')
export MANAGEMENT_USERNAME=$(kubectl get secret ${MANAGEMENT_AUTH_SECRET} --no-headers --ignore-not-found -n <CP4BA Namespace> -o jsonpath='{.data.username}' | base64 -d)
export MANAGEMENT_PASSWORD=$(kubectl get secret ${MANAGEMENT_AUTH_SECRET} --no-headers --ignore-not-found -n <CP4BA Namespace> -o jsonpath='{.data.password}' | base64 -d)

      Create BAI savepoints and store them in a temporary file called bai.json.

      curl -X POST -k -u ${MANAGEMENT_USERNAME}:${MANAGEMENT_PASSWORD} "${MANAGEMENT_URL}/api/v1/processing/jobs/savepoints" -o ./bai.json

       Scale down the CP4BA and Insights Engine Operator.

      oc scale --replicas=0 deployment ibm-cp4a-operator
oc scale --replicas=0 deployment ibm-insights-engine-operator

    • Retrieve the recovery path locations for each BAI component for which BAI savepoints are created from ./bai.json and update the bai_configuration section of the custom resource file. For Example: If there is a BAI savepoint being created for navigator component, then the updated custom resource file should have the below configuration.

      bai_configuration:
      navigator:
        recovery_path: /mnt/pv/savepoints/dba/bai-navigator/savepoint-fb88f4-42027046b73b
      ... 
      # Add recovery_path for all other components
    • Once the upgrade has been completed, make sure to remove all instances of the recovery_path parameters from the updated custom resource file.


    Actions: 
    From the branch that you cloned above navigate to the scripts directory and perform the following steps to upgrade the CP4BA operators and deployment.

    1. Upgrade the CP4BA operators.
      • Warning: 
        The script with the upgradeOperator option will scale the CP4BA Operators down to zero. You must execute the script with the upgradeDeploymentStatus mode to scale them back in. 

      • Actions:
        Run the cp4a-deployment.sh script with the upgradeOperator option to upgrade the IBM Cloud Pak foundational services/CP4BA operators:

        ./scripts/cp4a-deployment.sh -m upgradeOperator -n <CP4BA Namespace>

    2. Wait for the operators to complete their upgrades.
      By default all subscriptions are set to automatic, but if you have any subscriptions set to manual then you need to approve any pending InstallPlans.
      Use the below command to see the current status of the install plans.

      oc get installPlan

      The upgrade will be blocked, if any of the needed InstallPlans are not approved. It is not recommended to set subscriptions to manual as this makes the upgrade more error prone.

    3. You can use the following scripts to check the status of the upgrades.
      • Warning:
        The script will scale the CP4BA deployments down to zero. You must execute the cp4a-deployment.sh script with upgradeDeploymentStatus option to scale them back up.

      • Actions:
        [OPTIONAL] Run the cp4a-deployment.sh script with upgradeOperatorStatus option to check that the upgrade of the CP4BA operator and its dependencies is successful:

        ./scripts/cp4a-deployment.sh -m upgradeOperatorStatus -n <CP4BA Namespace>

    4. Start up the upgraded CP4BA Operators.
      Run the cp4a-deployment.sh script with upgradeDeploymentStatus option to check that the upgrade of the CP4BA deployment is successful:

      ./scripts/cp4a-deployment.sh -m upgradeDeploymentStatus -n <CP4BA Namespace>

       Note: If you are using the P8BPMREST CPE end point, you must wait for the CPE components status to display "Done" and then execute the below command to make it accessible.

      kubectl patch zenextension <CUSTOM_RESOURCE_FILENAME>-cpe-zen-extension -n <CP4BA NAMESPACE> --type=merge -p '{"metadata": {"annotations": {"checksum_cpe_ips": "0"}}}'
  • Scenario 9:  Your installed Production deployment is 24.0.1  GA or newer and using airgap/offline.

    Note:
    As prerequisites for this scenario, you must follow steps here to set up the bastion host to mirror images to the registry and further to set up the private registry.
    For a dedicated deployment or namespace scoped deployment, the value for < CP4BA Namespace >  should be the namespace where all IBM Cloud Pak foundational services/CP4BA Operators and Services are deployed. If the CP4BA Operators and Services are deployed in different namespaces( separation of duties), the value for < CP4BA Namespace > should be the namespace where all IBM Cloud Pak foundational services/CP4BA Operators are deployed in. 
    Warning:
    For a CP4BA Deployment with BAI ( Business Automation Insights ) selected as an optional component, it is recommended to create BAI savepoints before starting the upgrade process to this interim fix. For Flink event processing to resume from its previous state, savepoints are required to be created before the upgrade and specified in the updated CR. BAI savepoints can be created by following the below steps.

    •  Retrieve the name of the InsightsEngine custom resource file.

      InsightsEngine_CR=$(kubectl get InsightsEngine --no-headers --ignore-not-found -n <CP4BA-Namespace> -o name)
      Retrieve and export the below details.
      export MANAGEMENT_URL=$(kubectl get ${InsightsEngine_CR} --no-headers --ignore-not-found -n <CP4BA Namespace> -o jsonpath='{.status.components.management.endpoints[?(@.scope=="External")].uri}')
export MANAGEMENT_AUTH_SECRET=$(kubectl get ${InsightsEngine_CR} --no-headers --ignore-not-found -n <CP4BA Namespace> -o jsonpath='{.status.components.management.endpoints[?(@.scope=="External")].authentication.secret.secretName}')
export MANAGEMENT_USERNAME=$(kubectl get secret ${MANAGEMENT_AUTH_SECRET} --no-headers --ignore-not-found -n <CP4BA Namespace> -o jsonpath='{.data.username}' | base64 -d)
export MANAGEMENT_PASSWORD=$(kubectl get secret ${MANAGEMENT_AUTH_SECRET} --no-headers --ignore-not-found -n <CP4BA Namespace> -o jsonpath='{.data.password}' | base64 -d)

      Create BAI savepoints and store them in a temporary file called bai.json.

      curl -X POST -k -u ${MANAGEMENT_USERNAME}:${MANAGEMENT_PASSWORD} "${MANAGEMENT_URL}/api/v1/processing/jobs/savepoints" -o ./bai.json

       Scale down the CP4BA and Insights Engine Operator.

      oc scale --replicas=0 deployment ibm-cp4a-operator
oc scale --replicas=0 deployment ibm-insights-engine-operator

    • Retrieve the recovery path locations for each BAI component for which BAI savepoints are created from ./bai.json and update the bai_configuration section of the custom resource file. For Example: If there is a BAI savepoint being created for navigator component, then the updated custom resource file should have the below configuration.

      bai_configuration:
      navigator:
        recovery_path: /mnt/pv/savepoints/dba/bai-navigator/savepoint-fb88f4-42027046b73b
      ... 
      # Add recovery_path for all other components
    • Once the upgrade has been completed, make sure to remove all instances of the recovery_path parameters from the updated custom resource file.


    Actions:  
    Perform the following steps and then the upgrade of operators and deployments will start.

    1. To upgrade an airgap/offline Production deployment, find mirror file cp4ba-case-to-be-mirrored-24.0.1-IF007.txt for this interim fix from the branch that you cloned above under the scripts/airgap directory. Execute this command from your bastion host to download the CASE files:

      oc ibm-pak get -c file://(absolute path to file)/cp4ba-case-to-be-mirrored-24.0.1-IF007.txt

      The (absolute path to file) needs to be a path starting from "/". For example, "/opt".

    2. You will need to mirror the images associated with the new cp4ba-case-to-be-mirrored-24.0.1-IF007.txt mirror file. 

      export CASE_NAME=ibm-cp-automation
export CASE_VERSION=24.1.7
export CASE_INVENTORY_SETUP=cp4aOperatorSetup
export TARGET_REGISTRY=<target-registry>
export NAMESPACE=<cp4ba_namespace_name>

      Follow the instructions for either mirroring option in Mirroring images to the private registry using the new CASE version associated with this interim fix. If you are looking to install only a set of capabilities then you can make use of filters listed in Table 1 so that you can only download the specific set of images that you require. Please note that if the set of capabilities includes Business Automation Workflow, Process Federation Server, Workflow Process Service or Business Automation Insights make sure to include the filter "ibm_es_1_1_2470".

    3.  From the branch that you cloned above navigate to the scripts directory and perform the following steps to upgrade the CP4BA operators.
      • Warning: 
        The script with the upgradeOperator option will scale the CP4BA Operators down to zero. You must execute the script with the upgradeDeploymentStatus mode to scale them back in. 

      • Actions:
        Run the cp4a-deployment.sh script with the upgradeOperator option to upgrade the IBM Cloud Pak foundational services/CP4BA operators:
         

        ./scripts/cp4a-deployment.sh -m upgradeOperator -n <CP4BA Namespace>

    4. Wait for the operators to complete their upgrades.
      By default all subscriptions are set to automatic, but if you have any subscriptions set to manual then you need to approve any pending InstallPlans.
      Use the below command to see the current status of the install plans.

      oc get installPlan

      The upgrade will be blocked, if any of the needed InstallPlans are not approved. It is not recommended to set subscriptions to manual as this makes the upgrade more error prone.

    5. You can use the following scripts to check the status of the upgrades.

      • Warning:
        The script will scale the CP4BA deployments down to zero. You must execute the cp4a-deployment.sh script with upgradeDeploymentStatus option to scale them back up.

      • Actions:
        [OPTIONAL] Run the cp4a-deployment.sh script with upgradeOperatorStatus option to check that the upgrade of the CP4BA operator and its dependencies is successful:

        ./scripts/cp4a-deployment.sh -m upgradeOperatorStatus -n <CP4BA Namespace>

    6. Start up the upgraded CP4BA Operators.
      Run the cp4a-deployment.sh script with upgradeDeploymentStatus option to check that the upgrade of the CP4BA deployment is successful:

      ./scripts/cp4a-deployment.sh -m upgradeDeploymentStatus -n <CP4BA Namespace>

      Note: If you are using the P8BPMREST CPE end point, you must wait for the CPE components status to display "Done" and then execute the below command to make it accessible.

      kubectl patch zenextension <CUSTOM_RESOURCE_FILENAME>-cpe-zen-extension -n <CP4BA NAMESPACE> --type=merge -p '{"metadata": {"annotations": {"checksum_cpe_ips": "0"}}}'
 

Performing the necessary tasks after installation

 
a. Review the installation
It is recommended that you review the CR yaml status section and operator logs after the upgrade to ensure there are no failures preventing your pods from upgrading.
oc get icp4acluster icp4adeploy -o yaml > CP4BAconfig.yaml
oc logs deployment/ibm-cp4a-operator -c operator > operator.log
If you are interested in verifying the expected image digest for a particular image, then you can review the ibm-cp-automation\inventory\cp4aOperatorSdk\resources.yaml file in the CASE package. This file has a listing of the images managed by the CP4BA operator and their expected digest for this particular interim fix level.


 

Uninstalling

There is no procedure to uninstall the interim fix.
 

List of Fixes

APARs/Known Issues fixed by this interim fix are listed in the following tables.
 
The columns are defined as follows: 
 
Column titleColumn description
APAR/Known IssueThe defect number
TitleA short description of the defect
Sec.A mark indicates a defect related to security
Cont.A mark indicates a defect specific to the Cloud Pak integration of the component
B.I.A mark indicates the fix has a business impact. Details are found in the title column or the APAR/Known Issue document
 
General
Known IssueTitleSec.Cont.B.I.
N/A
Cloud Pak for Business Automation delivers container images that include operating system level and other open source libraries. Vulnerabilities (CVEs) for these libraries are published regularly.
This interim fix includes fixes for these libraries to address: 
 

CVE-2007-5686, CVE-2010-4756, CVE-2011-3374, CVE-2011-3389, CVE-2011-4116, CVE-2012-2663, CVE-2013-4392, CVE-2015-3276, CVE-2017-14159, CVE-2017-17740, CVE-2017-18018, CVE-2018-20796, CVE-2018-5709, CVE-2018-6829, CVE-2019-1010022, CVE-2019-1010023, CVE-2019-1010024, CVE-2019-1010025, CVE-2019-9192, CVE-2020-15719, CVE-2021-45346, CVE-2022-0563, CVE-2022-29458, CVE-2023-2953, CVE-2023-31437, CVE-2023-31438, CVE-2023-31439, CVE-2023-31486, CVE-2023-38552, CVE-2023-4016, CVE-2023-45143, CVE-2023-45853, CVE-2023-52426, CVE-2024-10041, CVE-2024-1013, CVE-2024-12243, CVE-2024-22365, CVE-2024-26458, CVE-2024-26461, CVE-2024-28757, CVE-2024-52533, CVE-2024-57699, CVE-2024-58251, CVE-2025-10966, CVE-2025-11226, CVE-2025-11579, CVE-2025-12758, CVE-2025-12817, CVE-2025-12818, CVE-2025-13034, CVE-2025-13465, CVE-2025-1352, CVE-2025-1365, CVE-2025-13699, CVE-2025-1372, CVE-2025-13836, CVE-2025-14819, CVE-2025-15284, CVE-2025-15558, CVE-2025-27587, CVE-2025-29088, CVE-2025-29481, CVE-2025-32365, CVE-2025-32414, CVE-2025-32415, CVE-2025-32988, CVE-2025-32989, CVE-2025-32990, CVE-2025-40777, CVE-2025-4373, CVE-2025-46394, CVE-2025-47906, CVE-2025-47907, CVE-2025-47911, CVE-2025-47912, CVE-2025-47914, CVE-2025-48976, CVE-2025-49574, CVE-2025-55130, CVE-2025-55131, CVE-2025-55132, CVE-2025-55163, CVE-2025-58056, CVE-2025-58057, CVE-2025-58098, CVE-2025-58181, CVE-2025-58183, CVE-2025-58185, CVE-2025-58186, CVE-2025-58187, CVE-2025-58188, CVE-2025-58189, CVE-2025-58436, CVE-2025-5914, CVE-2025-59375, CVE-2025-59465, CVE-2025-59466, CVE-2025-6020, CVE-2025-60876, CVE-2025-6141, CVE-2025-61723, CVE-2025-61724, CVE-2025-61725, CVE-2025-6176, CVE-2025-62727, CVE-2025-6297, CVE-2025-6395, CVE-2025-64512, CVE-2025-64720, CVE-2025-65018, CVE-2025-65082, CVE-2025-65945, CVE-2025-66019, CVE-2025-66034, CVE-2025-66200, CVE-2025-66221, CVE-2025-66453, CVE-2025-66560, CVE-2025-67221, CVE-2025-68616, CVE-2025-68938, CVE-2025-69223, CVE-2025-69224, CVE-2025-69225, CVE-2025-69226, CVE-2025-69227, CVE-2025-69228, CVE-2025-69229, CVE-2025-69230, CVE-2025-69413, CVE-2025-6965, CVE-2025-69725, CVE-2025-69873, CVE-2025-70559, CVE-2025-7425, CVE-2025-7709, CVE-2025-7962, CVE-2025-8058, CVE-2025-8194, CVE-2025-8732, CVE-2025-9230, CVE-2026-0798, CVE-2026-0897, CVE-2026-0994, CVE-2026-1225, CVE-2026-1584, CVE-2026-1669, CVE-2026-20736, CVE-2026-20750, CVE-2026-20800, CVE-2026-20883, CVE-2026-20888, CVE-2026-20897, CVE-2026-20904, CVE-2026-20912, CVE-2026-21637, CVE-2026-21860, CVE-2026-21968, CVE-2026-2219, CVE-2026-22690, CVE-2026-22691, CVE-2026-22702, CVE-2026-23490, CVE-2026-23745, CVE-2026-23950, CVE-2026-24281, CVE-2026-24308, CVE-2026-24486, CVE-2026-24688, CVE-2026-25210, CVE-2026-25639, CVE-2026-25896, CVE-2026-25990, CVE-2026-26007, CVE-2026-26278, CVE-2026-27024, CVE-2026-27025, CVE-2026-27026, CVE-2026-27199, CVE-2026-27205, CVE-2026-27448, CVE-2026-27459, CVE-2026-27601, CVE-2026-29111, CVE-2026-29786, CVE-2026-31802, CVE-2026-33056, CVE-2026-33231, CVE-2026-33236, CVE-2026-33349, CVE-2026-3479, CVE-2026-4427, CVE-2026-4437, CVE-2026-4438, DSA-6113-1, DSA-6132-1, DSA-6140-1, GHSA-6475-r3vj-m8vf, GHSA-jqcq-xjh3-6g23, RHSA-2025:11140, RHSA-2025:12447, RHSA-2025:12748, RHSA-2025:12876, RHSA-2025:13428, RHSA-2025:14130, RHSA-2025:16116, RHSA-2025:20559, RHSA-2025:20936, RHSA-2025:21255, RHSA-2025:23323, RHSA-2025:23343, RHSA-2025:23919, RHSA-2026:0126, RHSA-2026:0238, RHSA-2026:0312, RHSA-2026:0458, RHSA-2026:0492, RHSA-2026:0927, RHSA-2026:1408, RHSA-2026:1410, RHSA-2026:2042, RHSA-2026:2783, RHSA-2026:3405, RHSA-2026:3896, RHSA-2026:4165, RHSA-2026:4216

 
Previous interim fixes have included fixes which are also addressed with this interim fix. Consult the Related links section for readmes of previous interim fixes, at the bottom of this document.
X  
N/AIn addition to the list above and those related to a Known Issue listed in the following tables this interim fix addresses vulnerabilities listed in Security Bulletin: Multiple security vulnerabilities are addressed with IBM Cloud Pak for Business Automation iFixes for March 2026X  

 

Back to top

Cloud Pak for Business Automation Operator
Known IssueTitleSec.Cont.B.I.
DT455215During deployment of Business Automation Studio, the Task fails with unclear error: Error if target_env_name for default TOS is not dev_env_connection_definition   
DT464432Workflow operator fails during deployment with external IM URL   
DT460243Default self-signed certificates for legacy routes do not get renewed automatically when expired   

 

Back to top

Automation Document Processing
Known IssueTitleSec.Cont.B.I.
N/AN/A XX

 

Back to top

Automation Decision Services
Known IssueTitleSec.Cont.B.I.
N/AN/A   

 

Back to top

Known IssueTitleSec.Cont.B.I.
N/AN/A   

 

Back to top

Business Automation Insights
Known IssueTitleSec.Cont.B.I.
N/AN/A   

 

Back to top

Business Automation Navigator
Business Automation Studio
Known IssueTitleSec.Cont.B.I.
DT456161CVE-2025-27789 reported for runtime-7.25.7.tgz in web Process DesignerX  
DT461441Security vulnerability (CVE-2025-13465) in lodash lib affects IBM Workflow Center, Process Designer and Business Automation StudioX  
DT443522A NullPointerException Cannot invoke ''io.swagger.v3.oas.models.media.Schema.get$ref()'' because ''schema'' is null might occur during discovery or execution of a REST external service   
DT452033Unnamed Snapshot Deletion Fails via Swagger API   
DT455215During deployment of Business Automation Studio, the Task fails with unclear error: Error if target_env_name for default TOS is not dev_env_connection_definition   
DT455256Collaborators tab for Workflow is shown blank in IBM Business Automation Studio   
DT455293tw_authors with admin permissions cannot delete snapshots in Business Automation Studio   
DT457101Users cannot create Environment variables with names that contain dots   
DT457784Process Portal navigation fails to access saved searches when system is federated - IBM Business Automation Workflow   
DT458243Published snapshot becomes unpublished after branch deletion in IBM Business Automation Studio   
DT458398Process Portal slow to load after login due to repeated LSW_BRANCH queries in /rest/bpm/wle/v1/exposed API   
DT458582Process Designer hangs when opening heritage human service editor- IBM Business Automation Workflow   
DT461881Exported Localization Resource Does Not Reflect Updated Changes   
DT462586Exposed Automation Service (REST) omits null value properties from response payload after upgrade to V24.x   
DT463840install_packages DELETE API Does Not Remove Entries from LSW_DEPLOYMENT_PACKAGE Table   
DT464196When a contentObject is saved via a saveProperties call rolls back, the TWObject metadata on the retry will be null leading to a com.lombardisoftware.core.TeamWorksException   

 

Back to top

Business Automation Workflow including Automation Workstream Services
Known IssueTitleSec.Cont.B.I.
DT456161CVE-2025-27789 reported for runtime-7.25.7.tgz in web Process DesignerX  
DT458127CVE findings in a library called lz4-java-1.8.0.jar for Case EmittersX  
DT458920Multiple vulnerabilities in urllib3-2.5.0-py3-none-any.whlX  
DT459220CVE-2025-68429 in addon-actions-8.6.14.tgzX  
DT459901CVE-2026-22029 in router-1.23.0.tgz packaged with IBM Business Automation WorkflowX  
DT460287The Rhino jars packaged in Case Event emitter are vulnerableX  
DT460287The Rhino jars packaged in Case Event emitter are vulnerableX  
DT464292Update jquery-1.3.2.min.js to address multiple CVEsX  
DT465159Update immutable-5.1. to address CVE-2026-29063X  
DT422946Event Manager tasks are slow to execute and at times never complete, after upgrading to V24.0.0   
DT443522A NullPointerException Cannot invoke ''io.swagger.v3.oas.models.media.Schema.get$ref()'' because ''schema'' is null might occur during discovery or execution of a REST external service   
DT452849Task list is blank when navigated back to task list and task list refresh delay is enabled   
DT455841Doc: Users may notice that all baw-server pods get into 0/1 status when baw-server-0 is restarting - Cloud Pak for Business Automation   
DT457731Cannot use new provided models from watsonx.ai runtime that do not include max_output_tokens   
DT457784Process Portal navigation fails to access saved searches when system is federated - IBM Business Automation Workflow   
DT457911Slow performance when filtering process instances by 'Person' in Process Inspector   
DT457951Process instance migration fails due to unactivated TWObject   
DT458750CaseManager API returns the SQL query when invalid parameters are passed   
DT459023Username wraps onto next line in the comments dialog.   
DT459451The Case Client application fetches and loads static content slowly   
DT459460Preventing Script Injection in Rest Parameters   
DT459778Group members from Azure AD are unable to be returned by Workflow   
DT459828/home/forward-log.sh: line 48 /etc/filebeat/filebeat.yml: Read-only file system error when enabling Filebeat - Cloud Pak for Business Automation   
DT459876Using the Get REST API to access the Environment Variables of a Process Application or Toolkit fails with JAXBException   
DT460079Process Portal doesn't display Arabic characters on a Cloud Pak for Business Automation environment with MS SQL Server   
DT460222REST API /std/bpm/uca/event_manager_tasks/DELETE fails with CWTBG0019E error and Microsoft SQL syntax errors   
DT461680Case Lock is not happening when two users opening the same workitem in the Inbasket at the same time   
DT461716Business Automation Workflow (BAW) server is shut down when a large number of Business Automation Insights (BAI) messages buildup due to RecordTooLargeException   
DT461763When Federated Data Repository indexing is enabled, excessive updates occur on the FED_PARTITIONING_AGENT table   
DT462291A read timeout occurs on a call to saveProperties to update content properties on the IBM FileNet Content Platform Engine (CPE) server   
DT462586Exposed Automation Service (REST) omits null value properties from response payload after upgrade to V24.x   
DT463421Names are getting truncated in the UI if multiple users returned when reassigning a case to another user.   
DT463826Task cleanup performance improvement when deleting a large number of tasks.   
DT463998The existing configuration of Business Automation Workflow Case client plug-in gets wiped out every time the case-init job is run   
DT464196When a contentObject is saved via a saveProperties call rolls back, the TWObject metadata on the retry will be null leading to a com.lombardisoftware.core.TeamWorksException.   
DT464432Workflow operator fails during deployment with external IM URL   
DT464744Enabling audit logs for Process admin console changes yields incorrect JSON format   
DT464906Opening and closing work items from a user in-basket is slow due to retrieving repeated number of requests for retrieving choice lists   
DT464992CWTDS0037E: The credentials for the authentication alias 'EmbeddedECMTechnicalUser' are invalid   

 

Back to top

Enterprise Records
Known IssueTitleSec.Cont.B.I.
N/AN/A   

 

Back to top

FileNet Content Manager
Operational Decision Manager (based on ODM-9.0.0.1-IF022)
Known IssueTitleSec.Cont.B.I.
DT459790OUTPUT EXCEL FILE CONTAINS THE RULESET PARAMETERS IN AN INCORRECT ORDER   
DT457876PERFORMANCE SLOWNESS OF SIMULATION REPORTS TAB   
DT454985INCORRECT VALUES POPULATED IN THE EXCEL REPORT GENERATED WHEN RUNNING THE TEST SUITE   
DT458167UNEXPECTED ERROR USING THE DECISIONCENTER WEBHOOK NOTIFICATION   
DT459391TAB KEY IS NOT WORKING IN RULE DESIGNER B2X EDITOR   
DT457379SIMULATION CONFIGURATION COMPARISON DISPLAYS UNIX EPOCH FORMAT FOR DATE FIELD   
DT454837UNEXPECTED CAST EXCEPTION FOR BOOLEAN PROPERTY DURING RUNTIME RULE SELECTION   
DT458139UNABLE TO UPDATE STRUCT CUSTOM PROPERTY USING QUERY ACTION   
DT461021RULE DESIGNER DEBUGGER DOES NOT STOP ON BREAKPOINT IN RULES WITH SPACE IN NAME   
DT461796DEBUGGER DOES NOT STOP AT DECISION TABLE BREAKPOINT IN RULE DESIGNER   
DT462293BACKGROUND DELETION THROWS REFERENTIAL INTEGRITY CONSTRAINT VIOLATION   
DT460300MALFORMED SOAP REQUEST NOT RELEASED FROM XU POOL   
DT458698RULE UPDATE USING REMOTE API MIGHT NOT APPLY TO WORKING BASELINE PREVIOUSLY SET   
DT465307PLACEHODERS LOCATION IN COMPLETION LIST USING HIERARCHICAL MODE   
DT462733DIFFERENCES IN RULEAPP GENERATED FROM BUILDCOMMAND AND RULE DESIGNER   
DT459723IN DECISION TABLE COLUMN EDITOR THE PLACEHOLDERS ARE AT THE END OF THE COMPLETION LIST   
DT463396RESIZING THE BUSINESS CONSOLE WINDOW DOESN'T ALWAYS BEHAVE AS EXPECTED   
DT450186TECHNICAL RULE EDITOR IN RD DOES NOT SHOW TABS   

 

Back to top

User Management Service
Known IssueTitleSec.Cont.B.I.
N/AN/A   

Back to top

Workflow Process Service
Known IssueTitleSec.Cont.B.I.
DT459220CVE-2025-68429 in addon-actions-8.6.14.tgzX  
DT459901CVE-2026-22029 in router-1.23.0.tgz packaged with IBM Business Automation WorkflowX  
DT422946Event Manager tasks are slow to execute and at times never complete, after upgrading to V24.0.0   
DT443522A NullPointerException Cannot invoke ''io.swagger.v3.oas.models.media.Schema.get$ref()'' because ''schema'' is null might occur during discovery or execution of a REST external service   
DT455838DOC: Steps to setup static provisioning of PVCs for a Workflow Process Service deployment are not clear - Cloud Pak for Business Automation   
DT456413The Workflow Process Service datasave PVC should allow for RWX PV to be used, not just RWO   
DT457731Cannot use new provided models from watsonx.ai runtime that do not include max_output_tokens   
DT457911Slow performance when filtering process instances by 'Person' in Process Inspector   
DT457951Process instance migration fails due to unactivated TWObject   
DT460222REST API /std/bpm/uca/event_manager_tasks/DELETE fails with CWTBG0019E error and Microsoft SQL syntax errors   
DT461716Business Automation Workflow (BAW) server is shut down when a large number of Business Automation Insights (BAI) messages buildup due to RecordTooLargeException   
DT461763When Federated Data Repository indexing is enabled, excessive updates occur on the FED_PARTITIONING_AGENT table   
DT463826Task cleanup performance improvement when deleting a large number of tasks.   
DT464744Enabling audit logs for Process admin console changes yields incorrect JSON format   

 

Back to top

Cloud Pak for foundational services Operator
Known IssueTitleSec.Cont.B.I.
N/AN/A   

 

Back to top

Known Limitations

Document change history

  • 26 March 2026: Initial publish.

[{"Type":"MASTER","Line of Business":{"code":"LOB76","label":"Data Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSBYVB","label":"IBM Cloud Pak for Business Automation"},"ARM Category":[{"code":"a8m0z0000001gWWAAY","label":"Other-\u003ECloudPak4Automation Platform"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"24.0.1"}]

Document Information

Modified date:
26 March 2026

UID

ibm17259646

Page Feedback