# CVE-2026-14532: IBM WebSphere Application Server Liberty Integer Overflow

> An attacker with Reader role can trigger an uncaught exception via integer overflow, leading to information disclosure or denial of service.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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:** 13 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-3257-m328-3cx2

## What is CVE-2026-14532?

CVE-2026-14532 is a medium-severity vulnerability in IBM WebSphere Application Server - Liberty, published on 13 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

IBM WebSphere Application Server - Liberty 17.0.0.3 through 26.0.0.9 could allow a Reader-role attacker to obtain version information that causes an uncaught exception.

Weakness: CWE-190 (Integer Overflow or Wraparound)

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


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

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

## Is CVE-2026-14532 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-14532 is a medium-severity vulnerability in IBM WebSphere Application Server - Liberty, published on 13 Oct 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-14532 in the wild and no public exploit code.

Affected product: IBM WebSphere Application Server - Liberty. 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-14532/ (Markdown: https://insights.sbomify.com/CVE-2026-14532/index.md)
```

## Sources

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

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