Business Automation Workflow Containers And Traditional
Monthly
IBM Business Automation Workflow, in both its container and traditional (on-premises) distributions, fails to restrict XML external entity resolution when parsing XML data, allowing an authenticated remote user to read server-side files or exhaust process memory. The flaw carries a CVSS base score of 7.1 (AV:N/AC:L/PR:L/UI:N, C:H/I:N/A:L), meaning a low-privileged but valid account is required — it is not exploitable unauthenticated. IBM has published a vendor fix via support document node 7285930; there is no CISA KEV listing and no public exploit code identified at time of analysis, and no EPSS score was supplied with the intelligence feed.
XML External Entity (XXE) injection in IBM Business Automation Workflow containers and traditional deployments allows an authenticated remote attacker to read arbitrary files from the server or perform server-side request forgery due to vulnerable XML processing enabled by default in programming model artifacts. Affected versions span the 24.0.0, 24.0.1, 25.0.0, and 26.0.0 release lines, all below their respective latest interim fixes. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in CISA KEV.
IBM Business Automation Workflow (both containerized and traditional deployments) fails to enforce authorization checks on certain import operations, letting an authenticated user invoke restricted import actions they should not be permitted to perform. Successful abuse yields limited confidentiality and integrity impact (CVSS 5.4, AV:N/AC:L/PR:L/UI:N) rather than full system compromise. No public exploit code has been identified and the flaw is not listed in CISA KEV, but IBM has published a vendor patch, so unpatched deployments remain exposed to any user holding a valid low-privileged account.
Improper TLS hostname verification in IBM Business Automation Workflow exposes high-privilege sessions to man-in-the-middle interception by failing to validate that server certificates match the target hostname. Affected deployments span both containerized (Kubernetes/OpenShift) and traditional on-premises models across multiple release trains from 24.0.0 through 26.0.0. No public exploit has been identified and the vulnerability is not listed in CISA KEV; real-world risk is substantially bounded by the PR:H requirement - an attacker must already hold administrative credentials before exploitation is feasible.
IBM Business Automation Workflow, in both its container and traditional (on-premises) distributions, fails to restrict XML external entity resolution when parsing XML data, allowing an authenticated remote user to read server-side files or exhaust process memory. The flaw carries a CVSS base score of 7.1 (AV:N/AC:L/PR:L/UI:N, C:H/I:N/A:L), meaning a low-privileged but valid account is required — it is not exploitable unauthenticated. IBM has published a vendor fix via support document node 7285930; there is no CISA KEV listing and no public exploit code identified at time of analysis, and no EPSS score was supplied with the intelligence feed.
XML External Entity (XXE) injection in IBM Business Automation Workflow containers and traditional deployments allows an authenticated remote attacker to read arbitrary files from the server or perform server-side request forgery due to vulnerable XML processing enabled by default in programming model artifacts. Affected versions span the 24.0.0, 24.0.1, 25.0.0, and 26.0.0 release lines, all below their respective latest interim fixes. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in CISA KEV.
IBM Business Automation Workflow (both containerized and traditional deployments) fails to enforce authorization checks on certain import operations, letting an authenticated user invoke restricted import actions they should not be permitted to perform. Successful abuse yields limited confidentiality and integrity impact (CVSS 5.4, AV:N/AC:L/PR:L/UI:N) rather than full system compromise. No public exploit code has been identified and the flaw is not listed in CISA KEV, but IBM has published a vendor patch, so unpatched deployments remain exposed to any user holding a valid low-privileged account.
Improper TLS hostname verification in IBM Business Automation Workflow exposes high-privilege sessions to man-in-the-middle interception by failing to validate that server certificates match the target hostname. Affected deployments span both containerized (Kubernetes/OpenShift) and traditional on-premises models across multiple release trains from 24.0.0 through 26.0.0. No public exploit has been identified and the vulnerability is not listed in CISA KEV; real-world risk is substantially bounded by the PR:H requirement - an attacker must already hold administrative credentials before exploitation is feasible.