Memory corruption via unchecked font index
Published Sep 10, 2026 · Updated Sep 10, 2026
Heap-buffer overflow and use-after-free in libxls 1.6.3 allow attackers to corrupt memory by processing a crafted XLS file. xls_getCSS accepts a file-controlled font index without sufficient validation, causing out-of-bounds heap access and stale-pointer use. The flaw is reached when an application parses an untrusted XLS file; the published record establishes memory corruption but no more specific consequence.
Summary
What happened
Heap-buffer overflow and use-after-free in libxls 1.6.3 allow attackers to corrupt memory by processing a crafted XLS file. xls_getCSS accepts a file-controlled font index without sufficient validation, causing out-of-bounds heap access and stale-pointer use. The flaw is reached when an application parses an untrusted XLS file; the published record establishes memory corruption but no more specific consequence.
The record
- CVE
- CVE-2026-79591
- Published
- Sep 10, 2026
- Updated
- Sep 10, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1203
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 10, 2026CVE publishedPublication date reported by the CVE source.
- Sep 10, 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.
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
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
No public exploit references are available in this record.
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