Live › vulnerability › CVE-2026-111677
Go to dashboardAntiword through 0.37 has an inverted bounds check in vGet8LstInfo (prop8.c) when reading the PlcfLst record count. A crafted Word 8 .doc file can make it read past a heap allocation, which crashes the process.
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 on .doc files from users or external sources, for example in document conversion or indexing pipelines. Systems that never parse untrusted Word files can skip it. The description reports a crash; it does not claim code execution.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| antiword project antiword | vendor | <= 0.37 | – |
antiword -v or check the installed package version; affected if it is 0.37 or earlierUnknown from the sources.
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 heap out-of-bounds read vulnerability in vGet8LstInfo in prop8.c caused by an inverted bounds check on the PlcfLst record count. Attackers can supply a crafted Word 8 .doc file claiming up to 0xffff LSTF records in a tiny buffer, causing reads past the heap allocation that crash the process.
This page as .md · .json · in your agent: get_signal("CVE-2026-111677")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.