CVE-2026-111677
Received Received - Intake

Heap Out-of-Bounds Read in Antiword

Publication date: 2026-10-16

Last updated on: 2026-10-16

Assigner: VulnCheck

Description
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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-16
Last Modified
2026-10-16
Generated
2026-10-16
AI Q&A
2026-10-16
EPSS Evaluated
N/A
NVD
CVE-2026-111677
EUVD
EUVD-2026-102968

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
Adri van Os antiword 0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-125 The product reads data past the end, or before the beginning, of the intended buffer.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

Antiword through 0.37 has a heap out-of-bounds read flaw in the vGet8LstInfo function within prop8.c. This occurs due to an inverted bounds check on the PlcfLst record count. Attackers exploit this by crafting a malicious Word 8 .doc file that claims up to 0xffff LSTF records while using a tiny buffer. This causes the program to read past allocated memory, crashing the process.

Detection Guidance

Detecting this vulnerability requires analyzing files processed by antiword. Since antiword is a command-line tool, you can test it with a crafted Word document to see if it crashes. Create a test file with a high PlcfLst record count and run antiword on it. If the process crashes, the system may be vulnerable. Example command: antiword -x test.doc. Monitor for crashes or heap corruption when processing Word documents.

Impact Analysis

This vulnerability allows attackers to crash the antiword process by supplying a specially crafted Word document. Since antiword is no longer maintained, patched versions may not be available. The crash could disrupt document processing tasks but does not appear to enable code execution or data theft based on current analysis.

Mitigation Strategies

Since antiword is no longer maintained, the best mitigation is to stop using it. Replace it with actively maintained alternatives like LibreOffice or Pandoc for document conversion. If you must use antiword, restrict its use to trusted files only and monitor for crashes. Update to the latest version if a patch becomes available, though no patch is currently confirmed.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-111677. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart