Heap buffer overflow in dBASE index import
- Exploited
- No known exploitation
- Fix
- Fixed in < 26.2.6, < 26.8.1
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: < 26.2.6, < 26.8.1.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 5/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
LibreOffice's dBASE database driver contains a heap buffer overflow that a local attacker can trigger without logging in, though it requires the victim to open a crafted dBASE index file or folder as a data source. Successful exploitation could let an attacker read or change some data and disrupt the application's availability.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
LibreOffice includes a dBASE database driver, which reads dBASE tables and their .ndx index files when a folder of dBASE files is used as a data source. A heap buffer overflow existed when an index page was read. The number of entries recorded in a page was not checked against the number of entries the page could hold, which comes from a different field of the index header. A crafted index could also make a page refer back to itself, so that reading it recursed without end. In fixed versions the index header and the entry count of each page are limited to what an index page can hold, and a page that refers back to one of its parent pages is not followed.
cve.now Index
- Exploitation0/40No signal
- Exposure?/25Unknown. No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity5.4/10CVSS 5.4
- No patch0/5No signal
What would change the score
- Would score about 60 if added to CISA KEV
- Would score about 55 if CISA's SSVC rates exploitation active
- Would score about 27 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: < 26.2.6, < 26.8.1.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- The Document Foundation LibreOffice
From 26.2 · fixed in < 26.2.6; From 26.8 · fixed in < 26.8.1
Evidence 1
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-76181
Is CVE-2026-76181 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-76181?
LibreOffice: from 26.2 before < 26.2.6; from 26.8 before < 26.8.1.Source: cve.now feed data
How do I fix CVE-2026-76181?
Upgrade to a fixed version: < 26.2.6, < 26.8.1.Source: cve.now feed data