wvWare up to 1.2.9 FKP Run Count Validation wvGetPAPX_FKP/wvGetCHPX_FKP crun out-of-bounds

Summaryinfo

A vulnerability was found in wvWare up to 1.2.9. It has been classified as critical. Affected by this issue is the function wvGetPAPX_FKP/wvGetCHPX_FKP of the component FKP Run Count Validation. This manipulation of the argument crun causes out-of-bounds. This vulnerability is handled as CVE-2026-112055. The attack can be initiated remotely. There is not any exploit available.

Detailsinfo

A vulnerability classified as critical was found in wvWare up to 1.2.9. Affected by this vulnerability is the function wvGetPAPX_FKP/wvGetCHPX_FKP of the component FKP Run Count Validation. The manipulation of the argument crun with an unknown input leads to a out-of-bounds vulnerability. The CWE definition for the vulnerability is CWE-125. The product reads data past the end, or before the beginning, of the intended buffer. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

wvWare wv through 1.2.9 contains a stack-based out-of-bounds read vulnerability in wvGetPAPX_FKP and wvGetCHPX_FKP caused by an unvalidated FKP run count. Attackers can supply a crafted .doc file with a large crun value to read kilobytes past the 512-byte stack buffer, crashing applications like AbiWord.

The advisory is shared at hackmd.io. This vulnerability is known as CVE-2026-112055 since 10/18/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 10/19/2026).

The vulnerability scanner Nessus provides a plugin with the ID 367192 (Linux Distros Unpatched Vulnerability : CVE-2026-112055), which helps to determine the existence of the flaw in a target environment.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at Tenable (367192). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• wvWare

Version

• 1.2.0
• 1.2.1
• 1.2.2
• 1.2.3
• 1.2.4
• 1.2.5
• 1.2.6
• 1.2.7
• 1.2.8
• 1.2.9

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion