# CVE-2026-112056: wvWare wv through 1.2.9 Heap Out-of-Bounds Read via wvGetSTSH

> Attackers can crash applications using the wvWare library by supplying crafted Word documents with malformed stylesheets, causing a heap out-of-bounds read.

- **Severity:** Medium 6.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 18 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-112056, GHSA-jhv8-9974-jvpp, UBUNTU-CVE-2026-112056

## What is CVE-2026-112056?

CVE-2026-112056 is a medium-severity memory corruption vulnerability in wvWare wv, published on 18 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

wvWare wv through 1.2.9 contains a heap-based out-of-bounds read vulnerability in wvGetSTSH in stylesheet.c that allows attackers to crash applications by supplying crafted Word stylesheets. Attackers can provide a .doc file with ten or fewer styles or out-of-range style base indexes to read past heap arrays, crashing applications such as AbiWord.

Weakness: CWE-125 (Out-of-bounds Read)

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


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

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

## Is CVE-2026-112056 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-112056 is a medium-severity memory corruption vulnerability in wvWare wv, published on 18 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-112056 in the wild and no public exploit code.

Affected product: wvWare wv. 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-112056/ (Markdown: https://insights.sbomify.com/CVE-2026-112056/index.md)
```

## Sources

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

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