Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-63266 Overview
CVE-2026-63266 is a path traversal vulnerability [CWE-22] in LibreOffice Calc. The flaw allows a crafted spreadsheet to abuse the external data source linking feature and open an embedded Firebird database that writes files to arbitrary locations writable by the user.
An attacker delivers a malicious document that silently links to an embedded Firebird database. When the user opens the document and permits the link, Firebird can create or overwrite files outside its intended private directory. Fixed versions constrain the embedded Firebird database to its own private directory.
Critical Impact
A specially crafted LibreOffice Calc document can write files to any location the opening user has write access to, enabling tampering with user data or placement of files that aid follow-on attacks.
Affected Products
- LibreOffice (versions prior to the fix referenced in the vendor advisory)
- LibreOffice Calc with embedded Firebird database support
- Documents linked to external data sources using the Firebird engine
Discovery Timeline
- 2026-10-05 - CVE-2026-63266 published to NVD
- 2026-10-06 - Last updated in NVD database
Technical Details for CVE-2026-63266
Vulnerability Analysis
LibreOffice Calc supports linking a cell range to an external data source, with the link definition stored inside the spreadsheet file. When the link targets an embedded Firebird database, the database engine is invoked as part of resolving the link.
In vulnerable versions, the embedded Firebird database is not confined to a private working directory. Firebird can resolve relative or absolute paths supplied through the link and write files to any location the invoking user can access. This turns a data-link feature into an arbitrary file write primitive.
The root issue is improper limitation of a pathname to a restricted directory, which maps to [CWE-22]. The vendor fix restricts the embedded Firebird database to its own private directory for both read and write operations.
Root Cause
The embedded Firebird database engine inherited full filesystem write permissions from the LibreOffice process rather than being sandboxed to a per-document scratch directory. File paths carried through the external data source link were honored without canonicalization or containment checks.
Attack Vector
Exploitation requires local user interaction. The attacker delivers a Calc document through email, shared storage, or download. When the victim opens the document and allows the external data source link to resolve, the embedded Firebird database writes attacker-chosen files to writable paths within the user's security context.
The vulnerability does not grant code execution directly. The resulting file write primitive can be chained with other techniques, such as overwriting startup scripts, shell configuration files, or application data to achieve persistence or escalation. See the LibreOffice Security Advisory CVE-2026-63266 for vendor technical details.
Detection Methods for CVE-2026-63266
Indicators of Compromise
- Calc documents (.ods, .xlsx) containing external data source links that reference embedded Firebird databases from untrusted senders.
- Unexpected files created in user-writable paths (home directory, startup folders, shell initialization files) shortly after a LibreOffice session.
- soffice or soffice.bin process writing files outside the user's Documents directory or outside the Firebird private working directory.
Detection Strategies
- Inspect spreadsheet files statically for DatabaseRange or external data link entries referencing the Firebird driver.
- Correlate LibreOffice process execution with file-write telemetry targeting sensitive paths such as ~/.bashrc, ~/.config/autostart/, or %APPDATA%\Microsoft\Windows\Start Menu\Programs\Startup.
- Alert on LibreOffice child or helper processes creating executable or script files on disk.
Monitoring Recommendations
- Enable endpoint file-system auditing for the LibreOffice process tree and forward events to a central data lake.
- Monitor email and web gateways for spreadsheet attachments from external senders and sandbox-detonate suspicious samples.
- Track installed LibreOffice versions across the fleet and flag hosts running builds older than the vendor-fixed release.
How to Mitigate CVE-2026-63266
Immediate Actions Required
- Upgrade LibreOffice to the fixed version listed in the LibreOffice Security Advisory CVE-2026-63266.
- Instruct users not to enable external data source links in spreadsheets received from untrusted sources.
- Review recent LibreOffice file-write activity on sensitive endpoints for signs of exploitation.
Patch Information
The Document Foundation addressed the issue by restricting the embedded Firebird database so it can only open or create files inside its own private directory. Apply the fixed LibreOffice release referenced in the vendor advisory. No additional configuration is required once the patched build is installed.
Workarounds
- Open untrusted spreadsheets in a disposable virtual machine or sandboxed user account with no access to sensitive files.
- Disable or decline prompts for external data source updates when opening Calc documents from unverified senders.
- Restrict filesystem permissions for the account running LibreOffice to limit the blast radius of an arbitrary file write.
# Verify installed LibreOffice version on Linux
libreoffice --version
# Example: deny LibreOffice write access to shell init files via file ACLs
chmod 400 ~/.bashrc ~/.profile ~/.zshrc
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

