dbcve.org
Cloud Pak For Business AutomationApplication · Ibm

CVE-2025-36093

HIGH · 7.4 CVSS v3.1 Published 2025-11-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
83/100
Remediation priority · High
Remotely reachable No privileges 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, 24.0.1, and 24.0.0 could allow an attacker to access unauthorized content or perform unauthorized actions using man in the middle techniques due to improper access controls.

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 · moderate confidence

IBM Cloud Pak For Business Automation versions 24.0.0, 24.0.1, and 25.0.0 contains improper access controls that fail to properly authenticate or authorize requests, enabling man-in-the-middle attackers to intercept communications and potentially access unauthorized content or perform privileged actions.

MitigationApply IBM security patches for this vulnerability. Additionally, enforce TLS/SSL encryption for all communications and implement certificate validation to mitigate MITM attack vectors.

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

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

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. Identify IBM Cloud Pak For Business Automation version
    Run 'oc get icpa4 <instance-name> -o jsonpath={.status.version}' or check the IBM Cloud Pak UI under Administration > Instance Details for the installed version
    Affected if The installed version matches exactly 24.0.0, 24.0.1, or 25.0.0
  2. Verify no security patches applied
    Check IBM fix central or your internal patch management system for any installed security patches related to CVE-2025-36093
    Affected if No corresponding security patch for this CVE has been applied to the installation
  3. Confirm authentication configuration
    Review the IBM Cloud Pak authentication settings in the IBM Cloud Pak UI under User Access > Authentication or check the 'authentication' section in the deployment configuration
    Affected if Authentication is not properly enforced or configured for all API endpoints

You are affected if IBM Cloud Pak For Business Automation is installed at version 24.0.0, 24.0.1, or 25.0.0 without the CVE-2025-36093 security patch applied.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply IBM security patches for this vulnerability. Additionally, enforce TLS/SSL encryption for all communications and implement certificate validation to mitigate MITM attack vectors.

Recommended fix Moderate confidence

IBM Cloud Pak For Business Automation 25.0.1

  1. Verify the current IBM Cloud Pak For Business Automation version by accessing the Cloud Pak console or running 'cpctl utils version' command
  2. Review IBM Cloud Pak For Business Automation 25.0.1 release notes at www.ibm.com for changes and prerequisites
  3. Create a backup of current configuration and data
  4. Schedule a maintenance window for the upgrade
  5. Download IBM Cloud Pak For Business Automation 25.0.1 from IBM Fix Central (www.ibm.com/support/fixcentral)
  6. Follow IBM upgrade documentation to apply the update using 'cpctl utils upgrade' or the Cloud Pak console
  7. Verify the upgrade was successful and the vulnerability is resolved
Caveat Review 25.0.1 release notes for any configuration changes or deprecated features before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Cloud Pak For Business Automation Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-36093 — 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-36093 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