Quick answers
- Is CVE-2026-63270 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-63270 being exploited in the wild.
- How severe is CVE-2026-63270?
- Informational severity, published 5 October 2026.
- Which products and versions are affected?
- LibreOffice before 26.2.5 and before 26.8.0.
- Is there a fix for CVE-2026-63270?
- Yes: fixed in LibreOffice 26.2.5, LibreOffice 26.8.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-63270 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-63270?
- Check whether you run LibreOffice at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: LibreOffice 26.2.5, LibreOffice 26.8.0
Technical details
URLs in XForms instance data and Calc CSV/SQL data providers can undergo environment variable and INI file value expansion, allowing internal scheme URLs to be processed and their expanded values transmitted to attacker-controlled servers. The vulnerability exists because an earlier fix for CVE-2024-12426 did not address all code paths where documents supply URLs. The fix restricts such internal scheme URLs when originating from document content.
Affected products
- LibreOffice LibreOffice before 26.2.5 and before 26.8.0
Timeline
- 2026-10-05: disclosed