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.
Fix
Patch, vendor advisory and mitigation references on NVD 2
- https://hackmd.io/@haindpwn/antiword-word8-plcflst-count-and-fkp-run-oob-read Exploit, Mitigation, Third Party Advisory
- https://hackmd.io/@haindpwn/antiword-word8-plcflst-count-and-fkp-run-oob-read Exploit, Mitigation, Third Party Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 3
- Cpes+1 CPE criteria (now 1)NVD modified 2026-10-20 19:08
- StatusAwaiting Analysis → AnalyzedNVD modified 2026-10-20 19:08
- First seenCVSS 6.8NVD modified 2026-10-16 19:17
Affected (CPE criteria) 1
cpe:2.3:a:antiword_project:antiword:*:*:*:*:*:*:*:*
References 4
- https://github.com/rsdoiel/antiword/blob/fe4b579067122a2d9d62647efb1ee7cfe3ca92bb/prop8.c#L799-L825 Product
- https://hackmd.io/@haindpwn/antiword-word8-plcflst-count-and-fkp-run-oob-read Exploit, Mitigation, Third Party Advisory
- https://www.vulncheck.com/advisories/antiword-through-0.37-heap-out-of-bounds-read-via-vget8lstinfo-in-prop8-c Third Party Advisory
- https://hackmd.io/@haindpwn/antiword-word8-plcflst-count-and-fkp-run-oob-read Exploit, Mitigation, Third Party Advisory