Process crash via unchecked OLE directory indices
Published Mar 7, 2026 · Updated Mar 7, 2026
Out-of-bounds read in xlnt Community xlnt 1.6.0 through 1.6.1 allows local users to crash a process via a crafted encrypted XLSX file. The read_directory function uses file-supplied OLE directory indices to access parser structures without adequate bounds checks. The flaw is reached when an application linked to xlnt loads the malicious file, and the demonstrated consequence is a segmentation fault.
Summary
What happened
Out-of-bounds read in xlnt Community xlnt 1.6.0 through 1.6.1 allows local users to crash a process via a crafted encrypted XLSX file. The read_directory function uses file-supplied OLE directory indices to access parser structures without adequate bounds checks. The flaw is reached when an application linked to xlnt loads the malicious file, and the demonstrated consequence is a segmentation fault.
The record
- CVE
- CVE-2026-3664
- Published
- Mar 7, 2026
- Updated
- Mar 7, 2026
- Vendor
- xlnt Community
- Product
- xlnt
- Classifications
- CWE-119, CWE-125
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 7, 2026CVE publishedPublication date reported by the CVE source.
- Mar 7, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.6.0
- Affected versionversion=1.6.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- xl5 encrypted XLSX crash reproducerproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo