CVE-2026-13275 IBM MQ Managed File Transfer is vulnerable to XML external entity injection
High 7.1
Published
Updated
Check this codebase for CVE-2026-13275 and fix it if it is affected.
What it is: CVE-2026-13275 is a high-severity vulnerability in IBM MQ, published on 14 Sep 2026.
Exploitation: There is no known exploitation of CVE-2026-13275 in the wild and no public exploit code.
Affected product: IBM MQ. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2026-13275/ (Markdown: https://insights.sbomify.com/CVE-2026-13275/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-13275?
CVE-2026-13275 is a high-severity vulnerability in IBM MQ, published on 14 Sep 2026.
Official 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.
Weakness: CWE-611
Which versions are affected by CVE-2026-13275?
How do I fix CVE-2026-13275?
No fix has been published for CVE-2026-13275 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-13275 being exploited?
There is no known exploitation of CVE-2026-13275 in the wild and no public exploit code.
Sources
Also known as GHSA-47qx-f7xv-mh34.