Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NSummary
CVE-2025-36058 is a medium-severity Insertion of Sensitive Information into Externally-Accessible File or Directory (CWE-538) vulnerability in Ibm Business Automation Workflow. Its CVSS base score is 5.5 (Medium).
Operationally, ranked at the 1th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-6 (Least Privilege) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-3372
Vulnerability Data
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…
more
information in a config map.
- CWE(s)
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
Directly enforces access restrictions on the Kubernetes config map so that sensitive configuration data cannot be read by unauthorized container processes or users.
Requires least-privilege assignment so that only the minimal set of service accounts or pods are granted read access to the config map containing the sensitive IBM BAW settings.
Mandates cryptographic or other protection mechanisms for sensitive data stored at rest inside the config map, directly mitigating the disclosed configuration exposure.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Least-privilege file and directory permissions directly prevent unauthorized actors from reading sensitive data placed in accessible locations.
Protecting data-at-rest encompasses file-level access controls and encryption that stop exposure of sensitive information in externally reachable paths.
Hardened configuration baselines and ongoing config management reduce the chance that sensitive data is written to world-readable files or directories.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
By ensuring that only the minimum necessary data is present in files or directories that may be reachable by external parties, the control lowers the impact of any subsequent exposure.
Requiring visible or metadata labels on classified information helps ensure that files placed in externally accessible locations still carry an explicit sensitivity marker, lowering the likelihood of unnoticed exposure.
The control’s requirement to remove or securely destroy information stored in externally accessible locations reduces the risk of sensitive data being left in files or directories that external parties can reach.
Logging disposals, selecting vetted external disposal services, and protecting media according to classification reduce the likelihood that sensitive information ends up in externally accessible files or directories.
Verifying and sanitizing equipment prior to disposal or resale prevents sensitive files or directories from remaining accessible to external parties who later obtain the hardware.