Libxls is a C library for reading Microsoft Excel spreadsheets that, despite a narrow product scope, sits in the dependency chain of many document-processing and data-analysis applications across multiple platforms. The vendor's vulnerability footprint concentrates on memory-safety weaknesses characteristic of native code parsing: out-of-bounds writes, integer overflows, NULL-pointer dereferences, double-frees, and buffer-boundary violations that arise from the complexity of the legacy Excel binary format. The recurring nature of these classes reflects the demanding parsing requirements of malformed or adversarially crafted spreadsheet files, which can trigger memory corruption through a relatively low-barrier input vector. Defenders should track this vendor's releases and consider libxls exposure in document ingestion pipelines; current severity, exploitation, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Libxls Project over time
Signals from CVEs in this vendor scope (20 CVEs).
20 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2026-26824MEDIUM libxls through version 1.6.3 contains a use of uninitialized memory vulnerability in the OLE container parser. Memory allocated for the Master Sector Allocation Table (MSAT) in rea | Jun 3, 2026 | 6.5 | 28 | NO | NO |
CVE-2017-12108HIGH An exploitable integer overflow vulnerability exists in the xls_preparseWorkSheet function of libxls 1.4 when handling a MULBLANK record. A specially crafted XLS file can cause a m | Apr 24, 2018 | 8.8 | 27 | NO | NO |
CVE-2018-20452HIGH The read_MSAT_body function in ole.c in libxls 1.4.0 has an invalid free that allows attackers to cause a denial of service (application crash) or possibly have unspecified other i | Dec 25, 2018 | 8.8 | 26 | NO | NO |
CVE-2017-2896HIGH An exploitable out-of-bounds write vulnerability exists in the xls_mergedCells function of libxls 1.4. . A specially crafted XLS file can cause a memory corruption resulting in rem | Nov 20, 2017 | 7.8 | 26 | NO | NO |
CVE-2026-26825MEDIUM A use-of-uninitialized memory vulnerability exists in libxls 1.6.3 when parsing malformed XLS files. The issue is reachable via xls_parseWorkBook() and is triggered by uninitialize | Jun 3, 2026 | 5.3 | 25 | NO | NO |
CVE-2017-12110HIGH An exploitable integer overflow vulnerability exists in the xls_appendSST function of libxls 1.4.A specially crafted XLS file can cause memory corruption resulting in remote code e | Nov 20, 2017 | 7.8 | 25 | NO | NO |
CVE-2017-12109HIGH An exploitable integer overflow vulnerability exists in the xls_preparseWorkSheet function of libxls 1.4 when handling a MULRK record. A specially crafted XLS file can cause a memo | Apr 24, 2018 | 8.8 | 24 | NO | NO |
CVE-2021-27836MEDIUM An issue was discoverered in in function xls_getWorkSheet in xls.c in libxls 1.6.2, allows attackers to cause a denial of service, via a crafted XLS file. | Nov 3, 2021 | 6.5 | 23 | NO | NO |
CVE-2017-2910HIGH An exploitable Out-of-bounds Write vulnerability exists in the xls_addCell function of libxls 2.0. A specially crafted xls file can cause a memory corruption resulting in remote co | Dec 2, 2020 | 8.8 | 22 | NO | NO |
CVE-2018-20450MEDIUM The read_MSAT function in ole.c in libxls 1.4.0 has a double free that allows attackers to cause a denial of service (application crash) via a crafted file, a different vulnerabili | Dec 25, 2018 | 6.5 | 22 | NO | NO |
Signals from CVEs in this vendor scope (20 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Libxls Project.
Media articles that mention a CVE ID that affects a product developed by Libxls Project — matched by CVE ID, not by vendor name.