Live › vulnerability › CVE-2026-111678
Go to dashboardAntiword through 0.37 has a stack out-of-bounds read in the Word 8 property parsing code (vGet8PapInfo and vGet8ChrInfo in prop8.c) because FKP run counts and grpprl offsets are not bounded. An attacker who supplies a crafted .doc file can crash antiword or corrupt style parsing.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Teams that run antiword to convert Word .doc files, especially on a server or in a pipeline that processes uploads from outside. Systems that never open untrusted .doc files are unlikely to be exposed. unknown whether the sources list other exposed paths.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| antiword project antiword | vendor | <= 0.37 | – |
antiword -v or check the installed package version; affected releases are 0.37 and earlier.0.37 once a fixed version is published; the sources do not name one.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Antiword through 0.37 contains a stack out-of-bounds read vulnerability in vGet8PapInfo and vGet8ChrInfo in prop8.c because FKP run counts and grpprl offsets are not bounded. Attackers can supply a crafted .doc file with malicious FKP pages to read past the 512-byte stack buffer, crashing antiword or corrupting style parsing.
This page as .md · .json · in your agent: get_signal("CVE-2026-111678")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.