CVE-2026-104007: Code execution through the JDBC driver path of a database document

Published Nov 16, 2026
·
Updated

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.

Affected Software

1 affected component
The Document Foundation LibreOffice

Event History

Nov 16, 2026
CVE Published
via MITRE·04:40 PM
Data Sourced
via MITRE·04:40 PM
DescriptionWeakness

Frequently Asked Questions

1

What must an attacker include for exploitation to occur?

The attacker must craft a document containing a pivot table that uses a database document as its source. That database document must name a JDBC driver located in attacker-supplied content so LibreOffice loads and runs the Java code.

2

Does opening a crafted document immediately connect to the database source in fixed versions?

No. In fixed versions, a pivot table that references a database document by URL connects only after the user allows links to be updated.

3

What changes in fixed versions reduce the risk?

LibreOffice takes the JDBC driver location only from the user's driver configuration rather than from the database document. This prevents a database document from selecting an attacker-controlled driver location.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203