libpff through 20260926 Heap Out-of-Bounds Read via libpff_table_read_6c_record_entries
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fix or patch referenced
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
libpff, a library for reading Microsoft Outlook PST, OST, and PAB files, along with tools and bindings built on it such as pffexport and pypff, is affected. A specially crafted data file can cause these programs to read memory beyond the intended heap buffer, which may expose nearby memory contents or crash the application.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
libpff through 20260926 contains an off-by-one bounds check in libpff_table_read_6c_record_entries that allows attackers to trigger a heap out-of-bounds read via crafted 6c table record entries. Attackers can supply crafted PST, OST or PAB files to applications like pffexport or pypff to read adjacent heap memory or cause crashes.
Timeline
- CVE published
- First seen by cve.now
- Record last updated
Affected versions
- libyal libpff
through 20260926