CVE-2026-111678
Received Received - Intake

Stack Out-of-Bounds Read in Antiword via Malicious .doc File

Publication date: 2026-10-16

Last updated on: 2026-10-16

Assigner: VulnCheck

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

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-111678
EUVD
EUVD-2026-102969

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 stack out-of-bounds read flaw in functions vGet8PapInfo and vGet8ChrInfo within prop8.c. This occurs because FKP run counts and grpprl offsets are not properly validated. Attackers can exploit this by providing a malicious .doc file with specially crafted FKP pages, causing the program to read beyond a 512-byte stack buffer. This can lead to crashes or corruption during style parsing.

Impact Analysis

If you use antiword to process untrusted .doc files, this vulnerability could allow attackers to crash the program or corrupt memory. This might disrupt document processing tasks or enable further exploitation if combined with other flaws. The impact is limited to local execution since the attack requires user interaction with a malicious file.

Compliance Impact

This vulnerability does not directly impact compliance with GDPR, HIPAA, or similar regulations. However, if exploited to corrupt data or disrupt systems processing sensitive information (e.g., medical or personal records), it could indirectly lead to compliance violations. Organizations should patch antiword to mitigate potential risks.

Mitigation Strategies

Update antiword to the latest version or remove it if not needed. Avoid opening untrusted .doc files. Monitor for crashes or unusual behavior during document processing.

Chat Assistant

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

EPSS Chart