# CVE-2026-2310: XML external entity in webMethods Integration Server

> A remote attacker can exploit XML external entity injection in IBM webMethods Integration Server to expose sensitive information or consume memory resources.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Sep 2026
- **Updated:** 11 Sep 2026
- **Also known as:** GHSA-vxvc-4pm5-3rq9

## What is CVE-2026-2310?

CVE-2026-2310 is a high-severity vulnerability in IBM webMethods Integration Server, published on 10 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

IBM webMethods Integration Server 11.1 IBM webMethods Integration is vulnerable to an XML external entity injection (XXE) attack when processing XML data. A remote attacker could exploit this vulnerability to expose sensitive information or consume memory resources.

Weakness: CWE-91 (XML Injection)

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


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

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

## Is CVE-2026-2310 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-2310 is a high-severity vulnerability in IBM webMethods Integration Server, published on 10 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-2310 in the wild and no public exploit code.

Affected product: IBM webMethods Integration Server. 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-2310/ (Markdown: https://insights.sbomify.com/CVE-2026-2310/index.md)
```

## Sources

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

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