IBM Support

Readme for IBM Cloud Pak for Business Automation 24.0.1 IF008

Fix Readme


Abstract

The following document is for IBM Cloud Pak for Business Automation 24.0.1 IF008. 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 IF008
Fix ID:24.0.1-WS-CP4BA-IF008
Publication Date:25 June 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-IF008
  • Cloud Pak Foundational Services 4.18.1
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 IF008 branch by using the following git clone command.

    git clone -b 24.0.1-IF008 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-IF008.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-IF008.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-IF008.txt mirror file. 

      export CASE_NAME=ibm-cp-automation
export CASE_VERSION=24.1.8
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-IF008.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-IF008.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-IF008.txt mirror file. 

      export CASE_NAME=ibm-cp-automation
export CASE_VERSION=24.1.8
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-2017-1000383, CVE-2021-3782, CVE-2022-42889, CVE-2023-40403, CVE-2024-12086, CVE-2024-29371, CVE-2024-36124, CVE-2025-10158, CVE-2025-11965, CVE-2025-11966, CVE-2025-14009, CVE-2025-14505, CVE-2025-47273, CVE-2025-48734, CVE-2025-59375, CVE-2025-62718, CVE-2025-66293, CVE-2025-66506, CVE-2025-67030, CVE-2025-67721, CVE-2025-68146, CVE-2025-69534, CVE-2025-8677, CVE-2026-0846, CVE-2026-0847, CVE-2026-0848, CVE-2026-0865, CVE-2026-1002, CVE-2026-1519, CVE-2026-1525, CVE-2026-1526, CVE-2026-1528, CVE-2026-1839, CVE-2026-2003, CVE-2026-2004, CVE-2026-2005, CVE-2026-2006, CVE-2026-20706, CVE-2026-21710, CVE-2026-22007, CVE-2026-22013, CVE-2026-22016, CVE-2026-22018, CVE-2026-22021, CVE-2026-2229, CVE-2026-22555, CVE-2026-22701, CVE-2026-22772, CVE-2026-22815, CVE-2026-2359, CVE-2026-23831, CVE-2026-2391, CVE-2026-24051, CVE-2026-24117, CVE-2026-24137, CVE-2026-24791, CVE-2026-25087, CVE-2026-25547, CVE-2026-25646, CVE-2026-25714, CVE-2026-25749, CVE-2026-26231, CVE-2026-26996, CVE-2026-27137, CVE-2026-27138, CVE-2026-2739, CVE-2026-27489, CVE-2026-27628, CVE-2026-27783, CVE-2026-27888, CVE-2026-27904, CVE-2026-27942, CVE-2026-28208, CVE-2026-28351, CVE-2026-28417, CVE-2026-28421, CVE-2026-28500, CVE-2026-28699, CVE-2026-28737, CVE-2026-28744, CVE-2026-28780, CVE-2026-28804, CVE-2026-2950, CVE-2026-29518, CVE-2026-3039, CVE-2026-30922, CVE-2026-31826, CVE-2026-32597, CVE-2026-32952, CVE-2026-33007, CVE-2026-33036, CVE-2026-3304, CVE-2026-33123, CVE-2026-33155, CVE-2026-33230, CVE-2026-33231, CVE-2026-33236, CVE-2026-33349, CVE-2026-33412, CVE-2026-33532, CVE-2026-33540, CVE-2026-33699, CVE-2026-33747, CVE-2026-33748, CVE-2026-33809, CVE-2026-33810, CVE-2026-33816, CVE-2026-33857, CVE-2026-33871, CVE-2026-33916, CVE-2026-33937, CVE-2026-33938, CVE-2026-33939, CVE-2026-33940, CVE-2026-33941, CVE-2026-34032, CVE-2026-34059, CVE-2026-34268, CVE-2026-34282, CVE-2026-34445, CVE-2026-34446, CVE-2026-34447, CVE-2026-34513, CVE-2026-34514, CVE-2026-34515, CVE-2026-34516, CVE-2026-34517, CVE-2026-34518, CVE-2026-34519, CVE-2026-34520, CVE-2026-34525, CVE-2026-34591, CVE-2026-3497, CVE-2026-34982, CVE-2026-34993, CVE-2026-35029, CVE-2026-35030, CVE-2026-35172, CVE-2026-3520, CVE-2026-35204, CVE-2026-35205, CVE-2026-35206, CVE-2026-35385, CVE-2026-35386, CVE-2026-35387, CVE-2026-35388, CVE-2026-35414, CVE-2026-35469, CVE-2026-35535, CVE-2026-3592, CVE-2026-39852, CVE-2026-40175, CVE-2026-40192, CVE-2026-40217, CVE-2026-40260, CVE-2026-40347, CVE-2026-40895, CVE-2026-41035, CVE-2026-41066, CVE-2026-4111, CVE-2026-41140, CVE-2026-41168, CVE-2026-41242, CVE-2026-41245, CVE-2026-41312, CVE-2026-41313, CVE-2026-41314, CVE-2026-41409, CVE-2026-41635, CVE-2026-41650, CVE-2026-41888, CVE-2026-41889, CVE-2026-42033, CVE-2026-42034, CVE-2026-42035, CVE-2026-42036, CVE-2026-42037, CVE-2026-42038, CVE-2026-42039, CVE-2026-42040, CVE-2026-42041, CVE-2026-42042, CVE-2026-42043, CVE-2026-42044, CVE-2026-42198, CVE-2026-42203, CVE-2026-42208, CVE-2026-42264, CVE-2026-42271, CVE-2026-42305, CVE-2026-42309, CVE-2026-42310, CVE-2026-42311, CVE-2026-42561, CVE-2026-42578, CVE-2026-42579, CVE-2026-42778, CVE-2026-42779, CVE-2026-42945, CVE-2026-43618, CVE-2026-44017, CVE-2026-44018, CVE-2026-44019, CVE-2026-44020, CVE-2026-44022, CVE-2026-44023, CVE-2026-44288, CVE-2026-44289, CVE-2026-44290, CVE-2026-44291, CVE-2026-44292, CVE-2026-44293, CVE-2026-44294, CVE-2026-44486, CVE-2026-44487, CVE-2026-44488, CVE-2026-44490, CVE-2026-44492, CVE-2026-44494, CVE-2026-44495, CVE-2026-44496, CVE-2026-4519, CVE-2026-45536, CVE-2026-45740, CVE-2026-47214, CVE-2026-47265, CVE-2026-47734, CVE-2026-4775, CVE-2026-4786, CVE-2026-4800, CVE-2026-48068, CVE-2026-48069, CVE-2026-48522, CVE-2026-48524, CVE-2026-48525, CVE-2026-48526, CVE-2026-4867, CVE-2026-48710, CVE-2026-4923, CVE-2026-4926, CVE-2026-49468, CVE-2026-50269, CVE-2026-5160, CVE-2026-53537, CVE-2026-53538, CVE-2026-53539, CVE-2026-53540, CVE-2026-5946, CVE-2026-5950, CVE-2026-6100, CVE-2026-6321, CVE-2026-6322, CVE-2026-6476, CVE-2026-6638, CVE-2026-6861, CVE-2026-8723, GHSA-442j-39wm-28r2, GHSA-4gg8-gxpx-9rph, GHSA-69x8-hrgq-fjj8, GHSA-6v7p-g79w-8964, GHSA-7rx3-28cr-v5wh, GHSA-pjjw-68hj-v9mw, GHSA-q56x-g2fj-4rj6, GHSA-r4q5-vmmm-2653, GHSA-rf74-v2fm-23pw, GHSA-xmrv-pmrh-hhx2, RHSA-2026:11510, RHSA-2026:14791, RHSA-2026:18028, RHSA-2026:18693, RHSA-2026:18786, RHSA-2026:18957, RHSA-2026:18958, RHSA-2026:19175, RHSA-2026:19177, RHSA-2026:19216, RHSA-2026:19219, RHSA-2026:19220, RHSA-2026:19224, RHSA-2026:19363, RHSA-2026:19365, RHSA-2026:19368, RHSA-2026:21391, RHSA-2026:24367, RHSA-2026:24368, RHSA-2026:26410, RHSA-2026:5080, RHSA-2026:5602, RHSA-2026:6266, RHSA-2026:6390, RHSA-2026:6462, RHSA-2026:7302, RHSA-2026:7915, RHSA-2026:8075, RHSA-2026:8259, RHSA-2026:9686

 
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 June 2026X  

 

Back to top

Cloud Pak for Business Automation Operator
Known IssueTitleSec.Cont.B.I.
DT470197Kafka upgrade fails in Cloud Pak for Business Automation due to kafka-version annotation - IBM Cloud Pak for Business Automation   
DT471533Ephemeral storage for Flink components is not configurable - IBM Cloud Pak for Business Automation   
DT462338CPFS catalogsources left behind post upgrade   

 

Back to top

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

 

Back to top

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

 

Back to top

Known IssueTitleSec.Cont.B.I.
DT467513CVE-2026-33937 vulnerability in Handlebars.js libraryX  

 

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.
DT465383Update immutable-4.3.7.tgz to address CVE-2026-29063 BAS UIX  
DT465693GHSA-72hv-8253-57qq - jackson-core - bpm/Lombardi/libX  
DT467409Security vulnerabilities (CVE-2026-4800 & CVE-2026-2950) affect lodash libraryX  
DT467831Update axios-1.13. to address CVE-2025-62718, CVE-2026-40175X  
DT469417Multiple vulnerabilities in axios affects IBM Workflow center and Business Automation WorkflowX  
DT435315- You may notice a performance issue related to memory usage when load testing includes heritage human services that do not reach an end event   
DT439497Logging in as another user in the Inspector fails in 24.0.x   
DT443239Process Portal dashboard data is not visible   
DT449235Data section does not show value when debugging SQL service in Process Designer Inspector   
DT457824Incorrect default version option under Automation Service for Decision Automation in IBM Business Studio   
DT468563Chart colour inconsistency in Team Performance dashboard   
DT469116Snapshot Deployment Fails Due to System Toolkit Version Mismatch Between Process Application and Dependent Toolkit   
DT469335New Default Details UI or New Instance Owners UI wizard does not launch   
DT469396Unable to Step Into Client-Side Human Service During Remote Debugging   

 

Back to top

Business Automation Workflow including Automation Workstream Services
Known IssueTitleSec.Cont.B.I.
DT465319Update immutable to address CVE-2026-29063 PACX  
DT465383Update immutable-4.3.7.tgz to address CVE-2026-29063 BAS UIX  
DT465421Update storybook-8.6.15.tgz to address CVE-2026-27148X  
DT465428Update jetty-http-9.4.57.v20241219.jar to address CVE-2025-11143X  
DT465690GHSA-72hv-8253-57qq - jackson-core - IBM Business Automation Worfklow Business Automtion Insights Flink jobsX  
DT465693GHSA-72hv-8253-57qq - jackson-core - bpm/Lombardi/libX  
DT466609GHSA-72hv-8253-57qq - jackson-core - Business Automation WorfklowX  
DT467070GHSA-72hv-8253-57qq - jackson-core -Case Event Emitter- IBM Business Automation WorkflowX  
DT467311Need to update vulnerable Library - react-1.100.0.tgzX  
DT467409Security vulnerabilities (CVE-2026-4800 & CVE-2026-2950) affect lodash libraryX  
DT467457Update lodash-4.17.23.tgz to address CVE-2026-2950, CVE-2026-4800 - Process Admin ConsoleX  
DT467476Update picomatch-2.3.1.tgz to address CVE-2026-33671, CVE-2026-33672 - UMS/BTSX  
DT467480Security: update rsync to address CVE-2025-10158 workflow-server-case-initializationX  
DT467494Update requests-2.32. to address CVE-2026-25645 - BAW MLX  
DT467831Update axios-1.13. to address CVE-2025-62718, CVE-2026-40175X  
DT467841Update kafka-clients-3.9.1.jar to address CVE-2026-35554X  
DT469417Multiple vulnerabilities in axios affects IBM Workflow center and Business Automation WorkflowX  
DT469500Security: CVE-2026-40192X  
DT418302Dynamic Filtering doesn't work when " Show work item counts for all in-baskets" option in in-basket settings is selected -IBM Business Automation Workflow(BAW)   
DT435315- You may notice a performance issue related to memory usage when load testing includes heritage human services that do not reach an end event   
DT443239Process Portal dashboard data is not visible   
DT456747Object Store List Not loading in Business Automation Workflow Admin Desktop   
DT461228Authentication Repository assigned to a desktop gets reset to DOS everytime the case-init job is run   
DT463127JMS custom_xml settings are not applied for baw_configuration   
DT463715Federated Data Repository partitioning must be more resilient   
DT464334Removing the Workflow Liberty customization parameter from the CR does not remove the previously configured setting - Cloud Pak for Business Automation   
DT465541Properties are not displayed in the correct order within system-generated views when adding discretionary tasks from the Add Activity page   
DT465865Environment Variables REST API Returns Null in Liberty Workflow Server   
DT466758Clearing a date value from a Case property of datatype DateTime and saving the empty value at runtime does not reset the value to empty as expected   
DT466819Add Case Page validation errors not shown after updating to 24.0.1.0 IF006   
DT468563Chart colour inconsistency in Team Performance dashboard   
DT469116Snapshot Deployment Fails Due to System Toolkit Version Mismatch Between Process Application and Dependent Toolkit   
DT469335New Default Details UI or New Instance Owners UI wizard does not launch   
DT469396Unable to Step Into Client-Side Human Service During Remote Debugging   
DT470865Process instance migration fails in a network deployment environment with two or more cluster nodes due to ContentObjectMigrationService errors   
DT471701Case-init job resets the Server Base URL of the IBM Case Manager Web Application for all isolated regions   

 

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-IF026)
Known IssueTitleSec.Cont.B.I.
DT459490[RULE DESIGNER] DECISION CENTER CONNECTION LOST USING ZEN API KEY   
DT466101CANNOT CREATE EXCEL DOMAIN   
DT465516VARIABLES DO NOT APPEAR IN REST API OPTIONS WHEN USING HTDS VIEW OR DOWNLOAD   
DT471258UNCLEAR ERROR MESSAGE DURING COMPILATION   
DT470169DELETED CHILD NODES ARE DISPLAYED FOR HIERARCHY PROPERTY IN DECISION CENTER   
DT466661CANNOT EXECUTE SOAP REQUESTS WITH 7.0 AND 7.1 COMPATIBILITY MODES   
DT463767NO VALIDATION FOR INVALID INITIAL VALUE OF RULESET VARIABLES IN BUSINESS CONSOLE   
DT468317DECISION TABLE PRECONDITION NOT FULLY DISPLAYED   
DT466825MIGRATION SCRIPT MAY THROW EXCEPTIONS WHEN DROPPING AND RE-CREATING INDEXES   
DT469831ADD LASTVERSIONCOMMENT TO RESULTS WHEN USING DECISION CENTER REST API   
DT467438FAILURE RUNNING MIGRATION SCRIPT   
DT466051IMPOSSIBLE TO USE A 4 LETTERS LOCALE FOR DISPLAY LOCALE IN BUSINESS CONSOLE   
DT468866ILRSNAPSHOTIMPL INCOMPATIBLE WITH ILRBRANCH ERROR DURING MERGE   

 

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.
DT465319Update immutable to address CVE-2026-29063 PACX  
DT465421Update storybook-8.6.15.tgz to address CVE-2026-27148X  
DT465690GHSA-72hv-8253-57qq - jackson-core - IBM Business Automation Worfklow Business Automtion Insights Flink jobsX  
DT466609GHSA-72hv-8253-57qq - jackson-core - Business Automation WorfklowX  
DT467311Need to update vulnerable Library - react-1.100.0.tgzX  
DT467457Update lodash-4.17.23.tgz to address CVE-2026-2950, CVE-2026-4800 - Process Admin ConsoleX  
DT467841Update kafka-clients-3.9.1.jar to address CVE-2026-35554X  
DT463715Federated Data Repository partitioning must be more resilient   
DT470865Process instance migration fails in a network deployment environment with two or more cluster nodes due to ContentObjectMigrationService errors   

 

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

  • 25 June 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:
08 July 2026

UID

ibm17272398

Page Feedback