Application crash via attacker-sized stack allocation
Published Sep 15, 2026 · Updated Sep 15, 2026
Stack-based buffer overflow in GNU libextractor before 1.15 allows attackers to crash metadata-processing applications via a crafted StarOffice file. The process_star_office function sizes a variable-length stack array directly from an attacker-controlled OLE2 stream, permitting an allocation of up to 4 MB. The target must extract metadata from the malicious document; successful exploitation interrupts the extracting process through stack exhaustion.
Summary
What happened
Stack-based buffer overflow in GNU libextractor before 1.15 allows attackers to crash metadata-processing applications via a crafted StarOffice file. The process_star_office function sizes a variable-length stack array directly from an attacker-controlled OLE2 stream, permitting an allocation of up to 4 MB. The target must extract metadata from the malicious document; successful exploitation interrupts the extracting process through stack exhaustion.
The record
- CVE
- CVE-2026-91752
- Published
- Sep 15, 2026
- Updated
- Sep 15, 2026
- Vendor
- GNU
- Product
- GNU libextractor
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 15, 2026CVE publishedPublication date reported by the CVE source.
- Sep 15, 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=0 <1.15
What conditions does exploitation require?
What is affected?
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
No sourced classifications are available.
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