# CVE-2025-36374: IBM DataPower Gateway affected by XML external entity injection

> A privileged user can exploit XML external entity injection in IBM DataPower Gateway to expose sensitive information or consume memory resources.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Jul 2026
- **Updated:** 30 Jul 2026
- **Also known as:** GHSA-7pr3-cjqf-w984

## What is CVE-2025-36374?

CVE-2025-36374 is a medium-severity vulnerability in IBM DataPower Gateway 10.5.0, published on 30 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

IBM DataPower Gateway is vulnerable to an XML external entity injection (XXE) attack when processing XML data. A privileged user could exploit this vulnerability to expose sensitive information or consume memory resources.

Weakness: CWE-611 (Improper Restriction of XML External Entity Reference)

## Which versions are affected by CVE-2025-36374?


## How do I fix CVE-2025-36374?

No fix has been published for CVE-2025-36374 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-36374 being exploited?

There is no known exploitation of CVE-2025-36374 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-36374 and fix it if it is affected.

What it is: CVE-2025-36374 is a medium-severity vulnerability in IBM DataPower Gateway 10.5.0, published on 30 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-36374 in the wild and no public exploit code.

Affected product: IBM DataPower Gateway 10.5.0. 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-2025-36374/ (Markdown: https://insights.sbomify.com/CVE-2025-36374/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-36374
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-36374
- OSV: https://osv.dev/vulnerability/CVE-2025-36374

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-36374/
Summaries are generated and may contain mistakes; the official description above is the record.