Quick answers
- Is CVE-2026-76181 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-76181 being exploited in the wild.
- How severe is CVE-2026-76181?
- Informational severity, published 5 November 2026.
- Which products and versions are affected?
- LibreOffice before 26.2.6 and before 26.8.1.
- Is there a fix for CVE-2026-76181?
- Yes: fixed in LibreOffice 26.2.6, 26.8.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-76181 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-76181?
- Check whether you run LibreOffice at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: LibreOffice 26.2.6, 26.8.1
Technical details
A heap buffer overflow exists in the dBASE driver when parsing index (.ndx) files because the number of entries in an index page is not validated against the page's capacity. Additionally, circular references where a page points back to itself cause unbounded recursion. The fix validates index headers and entry counts to match page constraints and prevents following pages that reference their parents.
Affected products
- LibreOffice LibreOffice before 26.2.6 and before 26.8.1
Timeline
- 2026-11-05: disclosed