CVE-2026-87932: Arbitrary file write during DOCX export
LibreOffice Writer can save documents in DOCX format. A document can contain content controls whose values are bound to custom XML data, and that data is updated with the current values when the document is exported, including in a conversion run from the command line. Values taken from the document were not escaped where they were used, so a crafted document could write a file of its choosing anywhere the user can write when it was exported to DOCX. In fixed versions these values are written into the document directly, and the XSLT transformations LibreOffice runs can no longer write files or use the network.
Affected Software
Event History
Frequently Asked Questions
Who is exposed to this issue?
Users or automated processes that export untrusted or attacker-crafted Writer documents to DOCX are exposed. Command-line conversion runs are also affected, so unattended conversion services may be at risk if they process untrusted documents.
What does an attacker need to do to exploit it?
An attacker needs to provide a crafted document containing content controls bound to custom XML data and have it exported to DOCX by LibreOffice Writer. The resulting file write is limited to locations writable by the user or process performing the export.
Are network-based attacks involved?
The described issue is triggered during DOCX export rather than through a network request. Fixed versions prevent the XSLT transformations used during export from writing files or using the network.
What can be done if updating is not immediately possible?
Do not export untrusted documents to DOCX, including through command-line or automated conversion workflows. Run necessary conversions under an account with minimal filesystem write permissions to limit where a crafted document could write files.