CVE-2026-101352: The Document Foundation LibreOffice · Protection Mechanism Failure
Affects The Document Foundation LibreOfficeSource CVE Database V5
Not known to be exploited · CVSS 8.5 High.
Data as of 16 Nov 2026, 17:05 UTC
Thin evidence
One scorer or none| CNA (Document Fdn.) | CVSS 4.0 | 8.5 |
|---|
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 16 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| The Document FoundationLibreOffice | Affected
| Fixed in– |
AI-suggested
Users should upgrade to fixed versions of LibreOffice where document UI customizations are treated as macro content and subject to macro security settings. Until patched, users should avoid opening documents from untrusted sources and be cautious when interacting with document UI elements such as shortcuts and menus. There is no indication that other mitigations or workarounds are available.
Description
LibreOffice versions 26.2 and 26.8 contain a vulnerability where document-specific user interface customizations, such as keyboard shortcuts and menus, can execute macros or scripts even if macro security settings disallow macros. This allows a user interacting with a crafted document to run code without warning. The issue is addressed in fixed versions by treating these customizations like other macro content, enforcing macro security settings.