Heap-data disclosure via partially filled OLE buffers
Published Jun 3, 2026 · Updated Jun 3, 2026
Use of uninitialized memory in libxls 1.6.3 allows remote attackers to disclose heap data through a malformed XLS file. The OLE layer's ole2_read operation can leave short-read buffer regions uninitialized, and xls_parseWorkBook() then trusts those bytes. A consuming application must parse the crafted workbook; the documented consequence is limited to heap-data exposure and incorrect workbook state.
Summary
What happened
Use of uninitialized memory in libxls 1.6.3 allows remote attackers to disclose heap data through a malformed XLS file. The OLE layer's ole2_read operation can leave short-read buffer regions uninitialized, and xls_parseWorkBook() then trusts those bytes. A consuming application must parse the crafted workbook; the documented consequence is limited to heap-data exposure and incorrect workbook state.
The record
- CVE
- CVE-2026-26825
- Published
- Jun 3, 2026
- Updated
- Jun 3, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-908
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 3, 2026CVE publishedPublication date reported by the CVE source.
- Jun 3, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- Issue 156 MemorySanitizer reproductionproof 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