CVE-2025-13096: IBM Business Automation Workflow XXE Flaw

CVE-2025-13096 Overview

CVE-2025-13096 is an XML External Entity (XXE) injection vulnerability affecting IBM Business Automation Workflow containers and IBM Business Automation Workflow traditional. The flaw exists in the application's XML processing logic, where the underlying parser resolves external entities without restriction. An authenticated remote attacker can send crafted XML payloads to trigger the parser into reading sensitive files or exhausting memory resources on the server. IBM has acknowledged the issue and published a security advisory with remediation guidance.

Critical Impact
Authenticated remote attackers can disclose sensitive server-side information and cause partial denial of service by submitting malicious XML to vulnerable Business Automation Workflow endpoints.

Affected Products

IBM Business Automation Workflow containers V25.0.0 through V25.0.0-IF007
IBM Business Automation Workflow containers V24.0.0 through V24.0.0-IF007 and V24.0.1 through V24.0.1-IF007
IBM Business Automation Workflow traditional V25.0.0, V24.0.1, and V24.0.0

Discovery Timeline

2026-02-02 - CVE-2025-13096 published to NVD
2026-02-12 - Last updated in NVD database

Technical Details for CVE-2025-13096

Vulnerability Analysis

The vulnerability stems from improper handling of XML input within IBM Business Automation Workflow. The application's XML parser processes user-supplied documents while leaving external entity resolution enabled. An attacker with low-privilege network access can submit an XML document that defines and references an external entity. The parser then dereferences that entity during processing, returning the contents of local files or attempting outbound resource fetches.

XXE flaws map to [CWE-918] in this advisory, and the runtime behavior aligns with classic XML External Entity processing weaknesses. The attack does not require user interaction and operates over the network. Successful exploitation produces high confidentiality impact and limited availability impact. Integrity is not affected because the parser is read-only against external data sources.

Root Cause

The XML parser used by Business Automation Workflow does not disable Document Type Definition (DTD) processing or external entity expansion before parsing untrusted input. When a request reaches the affected XML handling routine, the parser substitutes SYSTEM entity references with the contents of the referenced URI. This default-permissive configuration is the underlying defect.

Attack Vector

An authenticated remote attacker sends an HTTP request containing an XML body to a workflow endpoint that parses XML. The payload defines an external entity pointing to a local file path such as file:///etc/passwd or an internal HTTP resource. The server reflects parsed content into a response or processes the entity in a way that exhausts memory, depending on the payload structure. Blind XXE variants using out-of-band channels are also feasible against network-reachable parsers.

No verified public proof-of-concept code is available for this CVE. Refer to the IBM Support Document for vendor-supplied technical details.

Detection Methods for CVE-2025-13096

Indicators of Compromise

Inbound HTTP requests to Business Automation Workflow endpoints carrying XML bodies that contain <!DOCTYPE> declarations or <!ENTITY> definitions with SYSTEM keywords
Unexpected outbound connections from Business Automation Workflow hosts to attacker-controlled domains, indicating out-of-band XXE exfiltration
Workflow process responses containing fragments of local system files such as /etc/passwd, win.ini, or internal configuration data
Sustained memory growth or out-of-memory errors in the workflow JVM correlated with XML processing requests

Detection Strategies

Inspect HTTP request bodies destined for workflow APIs for DOCTYPE declarations and external entity references using a web application firewall or reverse proxy
Monitor application logs for XML parser exceptions referencing entity resolution failures or SYSTEM identifier lookups
Correlate XML request volume with JVM heap metrics to surface resource-exhaustion attempts

Monitoring Recommendations

Enable verbose logging on XML-handling components and forward logs to a centralized analytics platform for retention and search
Baseline normal outbound network traffic from Business Automation Workflow hosts and alert on deviations to non-corporate destinations
Track authentication events for accounts submitting XML payloads, as exploitation requires valid credentials

How to Mitigate CVE-2025-13096

Immediate Actions Required

Apply the IBM-provided interim fix or upgrade to a fixed release as documented in the vendor advisory
Restrict network access to Business Automation Workflow administrative and API endpoints to trusted segments only
Audit recent XML processing activity for evidence of entity-based payloads and review user accounts with workflow submission privileges

Patch Information

IBM has published remediation details and fix availability in the IBM Support Document. Administrators should consult the advisory to identify the appropriate interim fix for each deployed version of the containers and traditional editions.

Workarounds

If immediate patching is not feasible, place a reverse proxy or API gateway in front of workflow endpoints to strip or reject XML payloads containing DOCTYPE or ENTITY declarations
Reduce the privilege level of the operating system account running the workflow process so that file reads via XXE return minimal sensitive data
Enforce strict input validation at the application boundary to reject XML content from low-trust users where business logic permits

bash

# Example reverse-proxy rule (NGINX + ModSecurity) to block DOCTYPE in XML bodies
SecRule REQUEST_HEADERS:Content-Type "@rx xml" \
    "id:1013096,phase:2,deny,status:400,\
     msg:'Blocked XXE attempt against IBM BAW',\
     chain"
    SecRule REQUEST_BODY "@rx (?i)<!DOCTYPE|<!ENTITY|SYSTEM\s+\"" \
        "t:none"