CVE-2026-13285: IBM MQ XXE Vulnerability

CVE-2026-13285 Overview

IBM MQ contains an XML External Entity (XXE) injection vulnerability triggered during processing of untrusted XML data. A remote authenticated attacker can craft malicious XML input that references external entities the parser resolves at parse time. Successful exploitation exposes sensitive information from the server or consumes memory resources, degrading availability. The weakness is classified under CWE-611: Improper Restriction of XML External Entity Reference. IBM has published a security advisory describing affected versions and remediation guidance.

Critical Impact
Authenticated remote attackers can read sensitive files accessible to the IBM MQ process and exhaust memory resources through crafted XML documents containing external entity references.

Affected Products

IBM MQ (see the IBM Security Advisory for the specific affected versions and fix packs)

Discovery Timeline

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

Technical Details for CVE-2026-13285

Vulnerability Analysis

The flaw resides in IBM MQ's XML parsing logic. The parser processes XML documents without disabling external entity resolution, which is the defining condition for XXE vulnerabilities. An authenticated attacker submits a crafted XML payload through an interface that reaches the vulnerable parser. The parser then dereferences attacker-controlled URIs declared inside a DOCTYPE block.

Exploitation requires network reach to the MQ service and low-privilege credentials. No user interaction is required. The confidentiality impact is high because the parser can be coerced to read local files and return their contents in error messages or response documents. Availability is affected when the attacker uses recursive or expansive entity definitions to inflate memory consumption.

Root Cause

The root cause is an insecurely configured XML parser that permits Document Type Definition (DTD) processing and external entity resolution. Secure defaults for Java and native XML parsers require disabling external-general-entities, external-parameter-entities, and DTD loading. When these features remain enabled on untrusted input, an attacker controls what the parser fetches and how it expands entities.

Attack Vector

An authenticated attacker sends a crafted XML document to an IBM MQ interface that accepts XML. The document declares an external entity referencing a local file path such as file:///etc/passwd or a URI reachable from the MQ host. When the parser resolves the entity, the referenced content is embedded in the response or logged, exposing sensitive data. Alternatively, the attacker declares nested parameter entities that expand exponentially, consuming memory until the process degrades or fails.

Refer to the IBM Security Advisory for full technical details and the list of vulnerable components.

Detection Methods for CVE-2026-13285

Indicators of Compromise

XML payloads containing <!DOCTYPE declarations or <!ENTITY definitions arriving at IBM MQ endpoints from untrusted sources.
Outbound network connections from the IBM MQ process to unexpected external hosts, indicating out-of-band XXE data exfiltration.
IBM MQ error logs referencing failed entity resolution, malformed DTDs, or parser exceptions tied to external URIs.
Sudden memory growth or out-of-memory conditions in the MQ queue manager process coinciding with XML message ingestion.

Detection Strategies

Inspect XML traffic at application gateways and Web Application Firewalls for DOCTYPE and ENTITY tokens targeting MQ endpoints.
Correlate authentication events for MQ users with subsequent parser errors or spikes in queue manager memory usage.
Baseline outbound connectivity from MQ hosts and alert on new destinations, particularly those matching URIs embedded in message payloads.

Monitoring Recommendations

Enable verbose parser logging on the MQ queue manager during triage to capture entity resolution attempts.
Forward MQ audit logs and host telemetry to a centralized analytics platform for correlation across authentication, network, and process telemetry.
Monitor process resource usage on MQ hosts and alert when memory consumption exceeds baseline thresholds.

How to Mitigate CVE-2026-13285

Immediate Actions Required

Apply the fix packs referenced in the IBM Security Advisory as soon as they are validated in a test environment.
Restrict network access to IBM MQ listeners so only trusted producers and consumers can submit XML messages.
Rotate credentials for MQ users if compromise is suspected, since exploitation requires authentication.
Review recent MQ logs for evidence of malformed XML or unexpected outbound connections from the MQ host.

Patch Information

IBM has published remediation guidance in the IBM Security Advisory. Administrators should identify their installed MQ version, cross-reference it with the advisory's affected versions table, and apply the corresponding interim fix or fix pack. Restart the queue manager after patching to load the corrected parser configuration.

Workarounds

If patching is delayed, place a validating XML gateway or WAF in front of MQ endpoints to strip DOCTYPE and ENTITY declarations from inbound messages.
Limit MQ channel authorization records so only vetted client applications can publish XML content to sensitive queues.
Apply egress filtering on MQ hosts to block outbound connections to arbitrary destinations, reducing out-of-band XXE data exfiltration paths.