# CVE-2025-14150: IBM webMethods Integration Sever is affected by

> Attackers can obtain sensitive user information from server responses in IBM webMethods Integration Server, requiring a vendor patch.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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:** 5 Feb 2026
- **Updated:** 5 Feb 2026
- **Also known as:** GHSA-ch6m-4rg5-6h78

## What is CVE-2025-14150?

CVE-2025-14150 is a medium-severity vulnerability in IBM webMethods Integration (on prem) - Integration Server, published on 5 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

IBM webMethods Integration (on prem) - Integration Server 10.15 through IS_10.15_Core_Fix2411.1 to IS_11.1_Core_Fix8 IBM webMethods Integration could disclose sensitive user information in server responses.

Weakness: CWE-497 (Exposure of Sensitive System Information to an Unauthorized Control Sphere)

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


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

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

## Is CVE-2025-14150 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-14150 is a medium-severity vulnerability in IBM webMethods Integration (on prem) - Integration Server, published on 5 Feb 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-2025-14150 in the wild and no public exploit code.

Affected product: IBM webMethods Integration (on prem) - 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-2025-14150/ (Markdown: https://insights.sbomify.com/CVE-2025-14150/index.md)
```

## Sources

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

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