Skip to main content
VulnerabilityPublished

CVE-2025-36058: IBM Business Automation Workflow containers · Insertion of Sensitive Information into Externally-Accessible File or Directory

Affects IBM Business Automation Workflow containersSource CVE Database V5

0

Not known to be exploited · CVSS 5.5 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
IBMBusiness Automation Workflow containersAffected
  • =25.0.0
  • =24.0.1
  • =24.0.0
Fixed in–

CPE configurations (6)

  • cpe:2.3:a:ibm:business_automation_workflow_containers:25.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:business_automation_workflow_containers:25.0.0:interim_fix_002:*:*:*:*:*:*
  • cpe:2.3:a:ibm:business_automation_workflow_containers:24.0.1:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:business_automation_workflow_containers:24.0.1:interim_fix_005:*:*:*:*:*:*
  • cpe:2.3:a:ibm:business_automation_workflow_containers:24.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:business_automation_workflow_containers:24.0.0:interim_fix_006:*:*:*:*:*:*

AI-suggested

  1. Restrict access to config maps and container orchestration management interfaces to trusted administrators only, using role-based access controls (RBAC) and network segmentation.
  2. Monitor and audit access logs for config maps and container configurations to detect unauthorized access attempts.
  3. Apply vendor patches or interim fixes as soon as they become available from IBM to remediate the vulnerability.
  4. Review and harden container deployment configurations to ensure sensitive information is not exposed unnecessarily, including using secrets management solutions instead of config maps for sensitive data.
  5. Implement strict local user access controls and minimize the number of users with local access to container hosts.
  6. Conduct regular security assessments and penetration testing focused on container environments to identify potential misconfigurations.
  7. Educate operational teams about the risks of exposing sensitive configuration data and best practices for container security.

Description

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.

References

Community reviews

Loading reviews…