CVE-2026-79591: n/a
CVE-2026-79591 is a heap-buffer-overflow and use-after-free vulnerability in the xls_getCSS() function of libxls version 1.6.3 and earlier. The flaw arises from insufficient validation of a file-controlled font index, which can lead to memory corruption.
AI Analysis
Technical Summary
This vulnerability exists in libxls 1.6.3 and earlier versions within the xls_getCSS() function. It is caused by inadequate validation of a font index controlled by the input file, resulting in a heap-buffer-overflow and use-after-free condition. These memory corruption issues could potentially be exploited if an attacker supplies a crafted XLS file to a system using the vulnerable library.
Potential Impact
The vulnerability could allow an attacker to cause memory corruption, potentially leading to application crashes or arbitrary code execution depending on the context in which libxls is used. However, no known exploits in the wild have been reported as of the publication date.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Users should monitor for official fixes or updates from the libxls maintainers and apply them once available. Until then, avoid processing untrusted XLS files with vulnerable versions of libxls.
CVE-2026-79591: n/a
Description
CVE-2026-79591 is a heap-buffer-overflow and use-after-free vulnerability in the xls_getCSS() function of libxls version 1.6.3 and earlier. The flaw arises from insufficient validation of a file-controlled font index, which can lead to memory corruption.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
This vulnerability exists in libxls 1.6.3 and earlier versions within the xls_getCSS() function. It is caused by inadequate validation of a font index controlled by the input file, resulting in a heap-buffer-overflow and use-after-free condition. These memory corruption issues could potentially be exploited if an attacker supplies a crafted XLS file to a system using the vulnerable library.
Potential Impact
The vulnerability could allow an attacker to cause memory corruption, potentially leading to application crashes or arbitrary code execution depending on the context in which libxls is used. However, no known exploits in the wild have been reported as of the publication date.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Users should monitor for official fixes or updates from the libxls maintainers and apply them once available. Until then, avoid processing untrusted XLS files with vulnerable versions of libxls.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- mitre
- Date Reserved
- 2026-08-25T00:00:00.000Z
- State
- PUBLISHED
Threat ID: 6aa3176191cc7f3848b51c07
Added to database: 09/10/2026, 20:47:29 UTC
Last enriched: 09/10/2026, 21:02:47 UTC
Last updated: 09/10/2026, 21:25:23 UTC
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.