CVE
The Document Foundation LibreOffice code execution via JDBC driver in database documents
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
- Exploited
- No known exploitation
- Fix
- Fixed in < 26.2.7, < 26.8.2
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. A spreadsheet uses a database as the source of a pivot table. The database document that describes the connection names the JDBC driver to use. The driver location is taken from the database document itself.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- 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? →
- 15/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- 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: total
Summary
In LibreOffice, a crafted database document can make the program load and run Java code that the document supplies when a user opens it. An attacker needs only local access and a user action, such as opening the file, and no login.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Original description
LibreOffice can connect to databases through JDBC drivers written in Java. A spreadsheet can use a database as the source of a pivot table, and the database document that describes the connection names the driver to use. The location the driver was loaded from was taken from the database document itself, so a crafted document could make LibreOffice load and run Java code that the document supplied when it was opened. This is a different route to the problem fixed for CVE-2026-63277. In fixed versions the driver location is taken only from the driver configuration of the user, and a pivot table whose source is a database document named by a URL connects only once the user allows links to be updated.
Who should check
Teams running LibreOffice that use spreadsheets with pivot tables sourced from database documents, or database documents that connect through Java JDBC drivers.
“LibreOffice can connect to databases through JDBC drivers written in Java.”
cve.now Index
- Exploitation0/40No signal
- Exposure5/25Specific setups only
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.5/10CVSS 8.5, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 25 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
A spreadsheet uses a database as the source of a pivot table. The database document that describes the connection names the JDBC driver to use. The driver location is taken from the database document itself.Upgrade to a fixed version: < 26.2.7, < 26.8.2.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-104007 (Code execution through the JDBC driver path of a database document), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-104007 (entry last updated 2026-11-17):
Affected:
- The Document Foundation LibreOffice: from 26.2, fixed in < 26.2.7; from 26.8, fixed in < 26.8.2
Fixed versions: < 26.2.7, < 26.8.2.
Conditions (all must be true for the bug to be hit):
- A spreadsheet uses a database as the source of a pivot table. (source: https://www.libreoffice.org/security/#cve-2026-104007)
- The database document that describes the connection names the JDBC driver to use. (source: https://www.libreoffice.org/security/#cve-2026-104007)
- The driver location is taken from the database document itself. (source: https://www.libreoffice.org/security/#cve-2026-104007)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: local access, no login, a user action.
CISA KEV: CVE-2026-104007 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-104007 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.libreoffice.org/about-us/security/advisories/cve-2026-104007
- https://www.libreoffice.org/security/#cve-2026-104007
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-104007
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-104007"}.Timeline
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- CVE published
- First seen by cve.now1 day
- Record last updated
Affected versions
- The Document Foundation LibreOffice
From 26.2 · fixed in < 26.2.7; From 26.8 · fixed in < 26.8.2
Evidence 3
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Link
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-104007
Is CVE-2026-104007 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
What does this mean?
A crafted database document can make LibreOffice load and run Java code that the document supplies when it is opened, so code runs on the machine when the document is opened.Source: libreoffice.org
Which versions are affected by CVE-2026-104007?
LibreOffice: from 26.2 before < 26.2.7; from 26.8 before < 26.8.2.Source: cve.now feed data
How do I fix CVE-2026-104007?
Upgrade to a fixed version: < 26.2.7, < 26.8.2. The vendor's advisory also recommends 26.2.7 or 26.8.2 or later.Source: cve.now feed data, libreoffice.org