Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCraft malformed .doc stylesheet
-
DeliveryDeliver file to victim
-
ExploitVictim opens file in wv-based app
-
ExecutionOut-of-bounds heap read in wvGetSTSH
-
ImpactApplication crashes (denial of service)
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, read limits
MITRE ATT&CK
1 technique across 1 tactic: Collection The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the victim to open an attacker-supplied Microsoft Word .doc file in an application built on the wv library (version through 1.2.9), such as AbiWord. The specific trigger is a Word stylesheet that either declares ten or fewer styles or carries out-of-range style base indexes, causing wvGetSTSH in stylesheet.c to read past heap arrays. Limiting factors: the attack vector is local (AV:L) and demands user interaction (UI:P) - the file must be delivered and opened - so there is no remote unauthenticated path; the impact is confined to crashing the parsing application (availability only), with no code execution or data disclosure established in the available data. |
| Impact | This is a denial-of-service issue, not a high-priority remote threat. The provided CVSS 4.0 vector (AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:H) scores 6.8 (Medium) and is internally consistent with the description: exploitation requires a local attack vector (a malicious .doc must reach and be opened by the victim's application) with passive user interaction, and the only impact is availability (VA:H) - a crash - with no confidentiality or integrity impact (VC:N/VI:N). Despite the CWE-125 (out-of-bounds READ) classification and the 'Information Disclosure' tag, the CVSS confidentiality metric is N and the description states the read merely crashes the application, so there is no confirmed data-leak primitive. No EPSS score, no CISA KEV listing, and no confirmed proof-of-concept flag were provided in the input, so this is classified as no public exploit identified at time of analysis - though the referenced hackmd writeup and the direct link to the vulnerable stylesheet.c line suggest technical analysis is public. The signals are consistent and point to a low-real-risk, crash-only bug in a niche document-parsing library rather than a widely exploitable vulnerability. Missing data: EPSS probability and any vendor fix version are absent from the input. |
| Exploit ScenarioDerived | An attacker crafts a malicious Microsoft Word .doc file whose stylesheet declares ten or fewer styles or contains out-of-range style base indexes, then delivers it to a victim (email attachment, download, shared drive). When the victim opens the file in an application that uses the wv library - such as AbiWord - wvGetSTSH reads past the end of a heap array and the application crashes. Public technical analysis of the flaw exists in the referenced writeup, but no confirmed weaponized exploit was indicated in the input. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 18, 2026
A crafted Microsoft Word .doc file can crash applications built on wvWare wv through 1.2.9 by triggering a heap-based out-of-bounds read in the wvGetSTSH stylesheet parser. The issue is local and requires the victim to open the malicious document; the assessed impact is availability-only, with no code execution or data disclosure established. No public exploit code or CISA KEV active exploitation was identified at time of analysis.
RemediationAI
No vendor-released patch identified at time of analysis. Until a fixed wv release is available, restrict or block untrusted .doc files from reaching wv-based applications: remove .doc file associations from AbiWord on endpoints that handle external documents, disable automatic preview or conversion of incoming .doc attachments, and open suspect files only in a disposable sandbox or low-privilege virtual machine. If legacy .doc support is required, route files through a maintained converter or content-disarm service that does not use wv 1.2.9, accepting that this changes document workflow and may alter formatting. Monitor the VulnCheck advisory at https://www.vulncheck.com/advisories/wvware-wv-through-1.2.9-heap-out-of-bounds-read-via-wvgetstsh and the upstream source at https://github.com/AbiWord/wv/blob/wv-1-2-9/stylesheet.c#L447 for a corrected release; applying a vendor patch is the only complete fix.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
CVE-2026-112056 is a CWE-125 out-of-bounds read in wvWare wv's Microsoft Word binary format parser. The STSH table in a .doc file describes stylesheet definitions, and wvGetSTSH in stylesheet.c around line 447 reads style records based on counts and base indexes without adequately validating them. A stylesheet with ten or fewer styles or out-of-range style base indexes causes the parser to walk past heap arrays, leading to a crash in consuming applications such as AbiWord. The CVSS 4.0 and assessed CVSS 3.1 vectors both describe local access and user interaction with availability-only impact; the assessed vector notes no privileges required and no confidentiality or integrity impact, and available data does not establish code execution or information disclosure.
Know when Wvware gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
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
A local crafted file must be opened by the user, so AV:L and UI:R with PR:N; impact is a crash only, giving A:H with C:N/I:N.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
DescriptionCVE.org
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.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Heap-based buffer overflow in the DecodeImage function in libwmf 0.2.8.4 allows remote attackers to cause a denial of se
meta.h in libwmf 0.2.8.4 allows remote attackers to cause a denial of service (out-of-bounds read) via a crafted WMF fil
Use-after-free vulnerability in libwmf 0.2.8.4 allows remote attackers to cause a denial of service (crash) via a crafte
Heap-based buffer overflow in libwmf 0.2.8.4 allows remote attackers to cause a denial of service (crash) or possibly ex
Stack-based out-of-bounds read in wvWare wv through 1.2.9 allows an unauthenticated local attacker to cause a client-sid
The wmf_malloc function in api.c in libwmf 0.2.8.4 allows remote attackers to cause a denial of service (application cra
EUVD-2026-103518
GHSA-jhv8-9974-jvpp
NVD
CVE.org
Exploit-DB