dbcve.org
Business Automation WorkflowApplication · Ibm

CVE-2025-36058

MEDIUM · 5.5 CVSS v3.1 Published 2026-01-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
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 Business Automation Workflow containers 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 006. IBM Cloud Pak for Business Automation and IBM Business Automation Workflow containers may disclose sensitve configuration information in a config map.

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 Business Automation Workflow containers and IBM Cloud Pak for Business Automation expose sensitive configuration information in a Kubernetes config map. This information disclosure vulnerability affects versions 24.0.0 through 24.0.0 IF006, 24.0.1 through 24.1.1 IF005, and 25.0.0 through 25.0.0 IF002. An attacker with access to the cluster could read the config map and obtain sensitive configuration data.

MitigationApply the appropriate Interim Fix (IF003 or later for v25.0.0, IF006 or later for v24.0.1, IF007 or later for v24.0.0) to remediate. Alternatively, audit and restrict access to config maps containing sensitive data and rotate any exposed credentials.

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
Business Automation WorkflowApplication
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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 BAW or Cloud Pak for BA installation
    Run 'kubectl get pods -A | grep -iE "baw|automation"' or check for IBM BAW-related namespaces and pods
    Affected if No IBM BAW or Cloud Pak for BA installation found means not affected
  2. Check installed version against affected ranges
    Run 'kubectl get deployment -A -o jsonpath="{.items[*].metadata.labels.app-version}"' or inspect the product version in the namespace where IBM BAW is installed. Compare to: 24.0.0-24.0.0 IF006, 24.0.1-24.1.1 IF005, or 25.0.0-25.0.0 IF002
    Affected if Version falls within any of the affected ranges (24.0.0 through 24.0.0 IF006, 24.0.1 through 24.1.1 IF005, or 25.0.0 through 25.0.0 IF002)
  3. Find config maps in the IBM BAW namespace
    Run 'kubectl get configmaps -n <baw-namespace>' to list all config maps in the namespace where IBM BAW is deployed
    Affected if Config maps exist in the IBM BAW namespace (required for vulnerability to apply)
  4. Inspect config maps for sensitive data
    Run 'kubectl get configmap <configmap-name> -n <baw-namespace> -o yaml' for each config map. Look for sensitive fields such as passwords, tokens, keys, credentials, or secrets in the data section
    Affected if Any config map contains sensitive configuration data such as passwords, tokens, keys, or credentials in plaintext

User is affected if IBM BAW or Cloud Pak for BA is installed, the version falls within the affected ranges (24.0.0-24.0.0 IF006, 24.0.1-24.1.1 IF005, or 25.0.0-25.0.0 IF002), and a config map in the BAW namespace contains sensitive credentials or configuration data that could be read by an attacker with cluster access.

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 Interim Fix (IF003 or later for v25.0.0, IF006 or later for v24.0.1, IF007 or later for v24.0.0) to remediate. Alternatively, audit and restrict access to config maps containing sensitive data and rotate any exposed credentials.

Fix this in Business Automation Workflow Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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