CVE-2025-36059
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 · uneditedIBM 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 could allow a local user with access to the container to execute OS system calls.
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 confidenceIBM Business Automation Workflow containers contain a vulnerability allowing a local user with container access to execute OS system calls on the host, representing a container escape/privilege escalation issue. The vulnerability affects specific versions across 24.0.0, 24.0.1, and 25.0.0 branches up to their respective Interim Fixes.
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= 24.0.0= 24.0.1= 25.0.0CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm IBM Business Automation Workflow is deployedCheck running containers or deployment manifests for IBM BAW container imagesAffected if IBM Business Automation Workflow container is present in the environment
-
Identify the installed BAW versionInspect the container image or running pod for version information - check image tags, labels, or run 'grep -r "24.0.0\|24.0.1\|25.0.0"' within the container metadataAffected if Version is 24.0.0, 24.0.1, or 25.0.0 without any Interim Fix applied
-
Verify Interim Fix statusCheck container filesystem or deployment documentation for presence of IF003 (for 25.0.0), IF006 (for 24.0.1), or IF007 (for 24.0.0)Affected if The relevant Interim Fix is NOT installed for the affected version in use
-
Review container security contextInspect pod/container runtime configuration for security settings: 'kubectl get pod <name> -o jsonpath={.spec.securityContext}' or docker inspect for privileged mode and user namespace settingsAffected if Container runs with privileged mode, as root user, or with host filesystem mount capabilities enabled
Environment is affected if IBM Business Automation Workflow version 24.0.0, 24.0.1, or 25.0.0 is running without the corresponding Interim Fix (IF007, IF006, or IF003) and the container has elevated privileges that enable host system call execution.
Generated from the published advisory. Verify against your own configuration.
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 dataApply the appropriate Interim Fix (IF003 for 25.0.0, IF006 for 24.0.1, IF007 for 24.0.0) from IBM to patch the vulnerability. Additionally, follow container security best practices: run containers with least privilege, avoid root users, and implement pod security policies/admission controls to limit container breakout impact.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-36059 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-36059 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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