dbcve.org
Cloud Pak For Business AutomationApplication · Ibm

CVE-2025-36094

HIGH · 8.1 CVSS v3.1 Published 2026-02-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
IBM Cloud Pak for Business Automation 25.0.0 through 25.0.0 Interim Fix 002, 24.0.1 through 24.0.1 Interim Fix 005, and 24.0.0 through 24.0.0 Interim Fix 007 could allow an authenticated user to cause a denial of service or corrupt existing data due to the improper validation of input length.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

IBM Cloud Pak for Business Automation versions 25.0.0 through 25.0.0 IF002, 24.0.1 through 24.0.1 IF005, and 24.0.0 through 24.0.0 IF007 contain an input validation vulnerability where authenticated users can provide improperly validated input lengths, leading to denial of service conditions or corruption of existing data within the platform.

MitigationApply the appropriate IBM Interim Fix (IF002 for 25.0.0, IF005 for 24.0.1, or IF007 for 24.0.0) from IBM to address the input length validation issue. Prior to deployment, test in a non-production environment to confirm the fix resolves the issue without introducing regressions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Cloud Pak For Business AutomationApplication
Affected:= 24.0.0= 24.0.1= 25.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine the installed IBM Cloud Pak for Business Automation version
    Use the IBM Cloud Pak utility or container inspection commands to query the deployed version. In OpenShift environments, run 'oc get icpa4 cp4a-operator' or inspect the operator deployment metadata. Check the 'spec.version' or image tags for the exact version number (such as 24.0.0, 24.0.1, or 25.0.0).
    Affected if The installed version is 24.0.0, 24.0.1, or 25.0.0 without the corresponding Interim Fix applied.
  2. Check if Interim Fix IF007 is applied for version 24.0.0
    Inspect the operator deployment or fix inventory. On version 24.0.0, run 'oc get icpa4 cp4a-operator -o jsonpath={.spec.version}' and cross-reference with IBM fix lists. Look for the presence of IF007 in the installed fixes or patch metadata.
    Affected if Running 24.0.0 without IF007 (or a later IF) means the input validation fix is not present.
  3. Check if Interim Fix IF005 is applied for version 24.0.1
    Inspect the operator deployment or fix inventory for version 24.0.1. Use the same inspection method as step 2 to identify if IF005 is listed among installed fixes.
    Affected if Running 24.0.1 without IF005 (or a later IF) means the input validation fix is not present.
  4. Check if Interim Fix IF002 is applied for version 25.0.0
    Inspect the operator deployment or fix inventory for version 25.0.0. Use the same inspection method to identify if IF002 is listed among installed fixes.
    Affected if Running 25.0.0 without IF002 (or a later IF) means the input validation fix is not present.
  5. Identify if authenticated users exist in the environment
    Review user accounts and role assignments in the IBM Cloud Pak for Business Automation admin console or LDAP integration settings. Use 'oc get users' or check the IBM Common Services user registry configuration.
    Affected if The vulnerability is exploitable by any authenticated user providing improperly validated input lengths, so the presence of non-admin users increases exposure risk.

You are affected if your IBM Cloud Pak for Business Automation is version 24.0.0 (without IF007), 24.0.1 (without IF005), or 25.0.0 (without IF002) and has authenticated users who can interact with input fields in the platform.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the appropriate IBM Interim Fix (IF002 for 25.0.0, IF005 for 24.0.1, or IF007 for 24.0.0) from IBM to address the input length validation issue. Prior to deployment, test in a non-production environment to confirm the fix resolves the issue without introducing regressions.

Fix this in Cloud Pak For Business Automation Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-36094 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-36094 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data