CVE-2026-13107: IBM Business Automation Workflow XXE Vulnerability

CVE-2026-13107 Overview

CVE-2026-13107 affects IBM Business Automation Workflow containers and traditional deployments. The product ships with programming model artifacts that parse XML without disabling external entity resolution by default. Attackers with low-privileged network access can submit crafted XML to trigger XML External Entity (XXE) processing, mapped to [CWE-611]. Successful exploitation can disclose sensitive files and induce limited availability impact on the affected workflow service.

Critical Impact
Authenticated network attackers can leverage default XML parsing behavior to read confidential data from the workflow server and degrade service availability.

Affected Products

IBM Business Automation Workflow (containers)
IBM Business Automation Workflow (traditional)
Programming model artifacts bundled with the above distributions

Discovery Timeline

2026-09-14 - CVE-2026-13107 published to the National Vulnerability Database
2026-09-16 - Last updated in NVD database

Technical Details for CVE-2026-13107

Vulnerability Analysis

The issue is an XML External Entity (XXE) injection in the default XML parsing configuration used by IBM Business Automation Workflow programming model artifacts. When the workflow engine processes XML input, the underlying parser resolves external entity references without restriction. An authenticated attacker can submit a crafted XML document that instructs the parser to fetch external resources or dereference local files.

The vulnerability compromises confidentiality by allowing retrieval of arbitrary readable files accessible to the workflow process. It also introduces limited availability impact through entity expansion or blocking external fetches. Integrity is not directly affected. Exploitation requires network reachability to the workflow endpoints and valid low-privileged credentials.

Root Cause

The root cause is insecure XML parser defaults in programming model artifacts. External entity resolution and DOCTYPE processing are not disabled, so the parser honors SYSTEM and parameter entity references contained in submitted XML. This behavior is inherited by any component that reuses the default parsing helpers.

Attack Vector

An authenticated user submits an XML payload to a workflow endpoint that processes XML through the vulnerable artifacts. The payload declares a DOCTYPE with an external entity pointing to a local file path or an out-of-band URL. When the parser resolves the entity, file contents are embedded in the response, echoed back through error messages, or exfiltrated to an attacker-controlled server through blind XXE techniques.

See the IBM Support Page for vendor-supplied technical details on the affected components and payload surface.

Detection Methods for CVE-2026-13107

Indicators of Compromise

Inbound XML payloads containing <!DOCTYPE> declarations or <!ENTITY> definitions referencing SYSTEM identifiers
Outbound DNS or HTTP requests from Business Automation Workflow hosts to unfamiliar external domains during XML processing
Workflow server reads of sensitive files such as /etc/passwd, credential stores, or configuration files outside normal application paths
Parser errors in workflow logs referencing entity expansion failures or unresolved external references

Detection Strategies

Inspect XML traffic to workflow endpoints for DOCTYPE and ENTITY tokens using web application firewall rules
Correlate authenticated workflow API sessions with anomalous outbound network connections originating from the workflow JVM
Baseline expected file access patterns for the workflow service account and alert on deviations

Monitoring Recommendations

Forward workflow application logs and network telemetry to a centralized analytics platform for correlation
Enable egress logging on hosts running Business Automation Workflow to identify blind XXE callbacks
Monitor authentication logs for low-privileged accounts issuing unusual XML-bearing requests at elevated volume

How to Mitigate CVE-2026-13107

Immediate Actions Required

Apply the IBM security update referenced on the IBM Support Page for CVE-2026-13107
Restrict network access to workflow endpoints so only trusted clients can submit XML content
Audit programming model artifacts in custom applications and rebuild them against patched libraries
Rotate credentials and secrets that may have been readable by the workflow process during the exposure window

Patch Information

IBM has published remediation guidance for IBM Business Automation Workflow containers and traditional deployments. Consult the vendor advisory for fix pack versions, iFix identifiers, and container image tags that address the insecure XML parser defaults.

Workarounds

Configure XML parsers used by custom programming model code to disable DOCTYPE declarations and external entity resolution
Set parser features http://apache.org/xml/features/disallow-doctype-decl to true and disable external-general-entities and external-parameter-entities
Deploy an inline gateway or WAF rule that rejects XML requests containing DOCTYPE or ENTITY declarations to workflow endpoints

bash

# Configuration example: block XML with DOCTYPE at a reverse proxy (NGINX)
location /workflow/ {
    if ($request_body ~* "<!DOCTYPE|<!ENTITY") {
        return 400;
    }
    proxy_pass http://baw_backend;
}