# CVE-2026-7366: IBM DataPower Gateway affected by HTTP request header leakage in XML-Firewall

> A race condition in IBM DataPower Gateway allows IP spoofing and disclosure of other clients' IP addresses due to improper isolation of request state.

- **Severity:** Medium 4.2 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Aug 2026
- **Updated:** 4 Oct 2026
- **Also known as:** GHSA-p6wq-xx5g-mm4g

## What is CVE-2026-7366?

CVE-2026-7366 is a medium-severity vulnerability in Ibm Datapower Gateway, published on 12 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

IBM DataPower Gateway 11.0.0.0 through 11.0.0.1 and IBM DataPower Gateway 10.5.0.0 through 10.5.0.21 and IBM DataPower Gateway 10.6.0.0 through 10.6.0.9 allows a race condition that results in improper isolation of request state when handling the built‑in X‑Client‑IP header. Under concurrent request processing, X‑Client‑IP values may be contaminated across requests, enabling IP spoofing and disclosure of other clients’ IP addresses.

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

## Which versions are affected by CVE-2026-7366?

It affects 1 product.


Products: Ibm Datapower Gateway.

## How do I fix CVE-2026-7366?

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

## Is CVE-2026-7366 being exploited?

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

## Other vulnerabilities in Ibm Datapower Gateway

- [CVE-2026-14269](https://insights.sbomify.com/CVE-2026-14269/): IBM DataPower Gateway Buffer Overflow (critical 9.8)
- [CVE-2026-14502](https://insights.sbomify.com/CVE-2026-14502/): IBM DataPower Gateway Improper Authentication (critical 9.8)
- [CVE-2026-14991](https://insights.sbomify.com/CVE-2026-14991/): IBM DataPower Gateway Out-of-bounds Write (critical 9.8)
- [CVE-2026-14992](https://insights.sbomify.com/CVE-2026-14992/): IBM DataPower Gateway Out-of-bounds Write (critical 9.8)
- [CVE-2026-15762](https://insights.sbomify.com/CVE-2026-15762/): IBM DataPower Gateway Out-of-bounds Write (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-7366 and fix it if it is affected.

What it is: CVE-2026-7366 is a medium-severity vulnerability in Ibm Datapower Gateway, published on 12 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-7366 in the wild and no public exploit code.

Affected product: Ibm Datapower Gateway. 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-7366/ (Markdown: https://insights.sbomify.com/CVE-2026-7366/index.md)
```

## Sources

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

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