# CVE-2026-123628: IBM webMethods Integration Server is vulnerable to sensitive information disclousure via admin/server/env API request.


- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 13 Nov 2026
- **Updated:** 16 Nov 2026
- **Also known as:** GHSA-2ch9-693p-5rhw

## What is CVE-2026-123628?

CVE-2026-123628 is a high-severity vulnerability in IBM webMethods Integration Server, published on 13 Nov 2026. 

### Official description

IBM webMethods Integration Server 10.15 and 11.1 could allow a remote attacker to obtain sensitive information due to an exposure of sensitive server-side environment variables and Java runtime details.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: IBM webMethods Integration Server.

CPE match criteria (CPE 2.3):

- `cpe:2.3:a:ibm:webmethods_integration_server:10.15:*:*:*:*:*:*:*` from 10.15 up to 10.15_Core_Fix2
- `cpe:2.3:a:ibm:webmethods_integration_server:10.15:*:*:*:*:*:*:*` from 11.1 up to 11.1_Core_Fix11
- `cpe:2.3:a:ibm:webmethods_integration_server:11.1:*:*:*:*:*:*:*` from 10.15 up to 10.15_Core_Fix2
- `cpe:2.3:a:ibm:webmethods_integration_server:11.1:*:*:*:*:*:*:*` from 11.1 up to 11.1_Core_Fix11

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

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

## Is CVE-2026-123628 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-123628 is a high-severity vulnerability in IBM webMethods Integration Server, published on 13 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-123628 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-123628/ (Markdown: https://insights.sbomify.com/CVE-2026-123628/index.md)
```

## Sources

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

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