Description

IBM MQ 9.1.0.0 through 9.1.0.37 LTS, 9.2.0.0 through 9.2.0.43 LTS, 9.3.0.0 through 9.3.0.41 LTS, 9.3.0.0 through 9.3.5.1 CD, 9.4.0.0 through 9.4.0.25 LTS, 9.4.0.0 through 9.4.5.1 CD, and 10.0.0.0 Managed File Transfer could allow an authenticated attacker to read arbitrary files or perform server-side request forgery due to XML external entity injection in reply message processing.

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "7.1",
  "pubDate": "2026-09-14T21:17:01.393Z",
  "pubdate": "2026-09-14T21:17:01.393Z",
  "executiveSummary": "An XML External Entity (XXE) injection vulnerability exists in IBM MQ Managed File Transfer (MFT) components. This vulnerability allows an authenticated attacker to perform unauthorized file system access or execute Server-Side Request Forgery (SSRF) attacks. The flaw stems from improper processing of XML data within reply messages, which fails to securely parse or restrict external entity references. By crafting malicious XML payloads, an attacker can coerce the application into reading sensitive local files or interacting with internal or external network resources, effectively bypassing standard security perimeters. The vulnerability impacts multiple long-term support (LTS) and continuous delivery (CD) versions of IBM MQ. Given the potential for data exfiltration and network reconnaissance, this issue poses a significant risk to the confidentiality and integrity of the messaging infrastructure. Successful exploitation requires an authenticated attacker capable of interacting with the affected message processing functions.",
  "technicalDetails": "The vulnerability is rooted in the XML parsing logic utilized by the IBM MQ Managed File Transfer (MFT) component during the processing of reply messages. The underlying XML parser is improperly configured, failing to disable the resolution of external entities and document type definitions (DTDs). Consequently, when the application processes a specially crafted XML document containing a crafted DOCTYPE declaration, the parser attempts to resolve external references defined by the attacker.\nThe attack flow begins with an authenticated attacker submitting a malicious reply message to the targeted MFT service. This message includes an XML payload containing an internal or external entity definition referencing a target file path (e.g., /etc/passwd or application configuration files) or a network URL. Upon receipt, the MFT component parses the XML, causing the XML parser to fetch the referenced content. If the content is a file, the parser may return the contents of the file within the application response, leading to arbitrary file disclosure. If a network URL is provided, the parser triggers an outbound request, facilitating SSRF, which can be leveraged to scan internal networks or interact with services restricted to the host's loopback interface.\nAffected versions include: IBM MQ 9.1.0.0 through 9.1.0.37 LTS, 9.2.0.0 through 9.2.0.43 LTS, 9.3.0.0 through 9.3.0.41 LTS, 9.3.0.0 through 9.3.5.1 CD, 9.4.0.0 through 9.4.0.25 LTS, 9.4.0.0 through 9.4.5.1 CD, and 10.0.0.0 Managed File Transfer. The vulnerability is triggered during the routine handling of XML data structures within MFT messages. Exploitation is contingent upon the attacker's ability to supply messages that are processed by the vulnerable parser. Because the component performs this processing automatically upon message consumption, the impact is high, as it allows for the exfiltration of system-sensitive data or the exploitation of internal network resources. The lack of validation and sanitization regarding entity references allows the payload to bypass security controls, leading to potential credential theft, information disclosure, or further lateral movement within the production environment."
}