# CVE-2026-91752: GNU libextractor before 1.15 Stack Overflow via OLE2

> Attackers can crash applications using GNU libextractor by sending malicious StarOffice documents that trigger a stack overflow.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** DEBIAN-CVE-2026-91752, GHSA-vrwm-2jf2-f6fv, UBUNTU-CVE-2026-91752

## What is CVE-2026-91752?

CVE-2026-91752 is a high-severity memory corruption vulnerability in GNU libextractor, published on 15 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

GNU libextractor before 1.15 contains a stack-based buffer overflow vulnerability in the process_star_office function that sizes a variable-length stack array from attacker-controlled OLE2 stream data. Attackers can craft malicious StarOffice documents that allocate up to 4 MB on the stack, causing stack overflow and crashing any application extracting metadata from the document.

Weakness: CWE-789 (Memory Allocation with Excessive Size Value)

## Which versions are affected by CVE-2026-91752?


## How do I fix CVE-2026-91752?

Upgrade to a fixed version.

## Is CVE-2026-91752 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-91752 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-91752 and fix it if it is affected.

What it is: CVE-2026-91752 is a high-severity memory corruption vulnerability in GNU libextractor, published on 15 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-91752 exists.

Affected product: GNU libextractor. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-91752/ (Markdown: https://insights.sbomify.com/CVE-2026-91752/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-91752
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-91752
- OSV: https://osv.dev/vulnerability/CVE-2026-91752

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-91752/
Summaries are generated and may contain mistakes; the official description above is the record.