CVE
The Document Foundation LibreOffice macro protection bypass in document shortcuts and menus
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
- Exploited
- No known exploitation
- Fix
- Fixed in < 26.2.7, < 26.8.2
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. The document carries its own user interface customizations (keyboard shortcuts, menus or toolbars) with macro or script commands bound to them. The macro security settings do not allow the macros of the document.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 15/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
A crafted document can carry its own keyboard shortcuts, menus and toolbars that run macros or scripts even when the document's macro security settings would block them. In LibreOffice, a local attacker can run code without any warning if a user presses a shortcut or picks a menu item in that document, which requires user interaction.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Original description
A document can carry its own user interface customizations, such as keyboard shortcuts, menus and toolbars, which take effect while the document is open. A command bound in these customizations could run a macro or a script even when the macro security settings did not allow the macros of the document, so a user who pressed a shortcut or chose a menu item in a crafted document could run code without any warning. In fixed versions the customizations of a document are treated like its other macro content, and the macro and script commands in them are only kept when the macros of the document are allowed.
Who should check
Teams running LibreOffice that open documents from untrusted sources; fixed in LibreOffice 26.2.7 and 26.8.2.
“Fixed in : LibreOffice 26.2.7/26.8.2”
cve.now Index
- Exploitation0/40No signal
- Exposure5/25Specific setups only
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.5/10CVSS 8.5, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 25 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
The document carries its own user interface customizations (keyboard shortcuts, menus or toolbars) with macro or script commands bound to them. The macro security settings do not allow the macros of the document.Upgrade to a fixed version: < 26.2.7, < 26.8.2.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-101352 (Macros run from a document's own shortcuts, menus and toolbars), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-101352 (entry last updated 2026-11-17):
Affected:
- The Document Foundation LibreOffice: from 26.2, fixed in < 26.2.7; from 26.8, fixed in < 26.8.2
Fixed versions: < 26.2.7, < 26.8.2.
Conditions (all must be true for the bug to be hit):
- The document carries its own user interface customizations (keyboard shortcuts, menus or toolbars) with macro or script commands bound to them. (source: https://www.libreoffice.org/security/#cve-2026-101352)
- The macro security settings do not allow the macros of the document. (source: https://www.libreoffice.org/security/#cve-2026-101352)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: local access, no login, a user action.
CISA KEV: CVE-2026-101352 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-101352 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.libreoffice.org/about-us/security/advisories/cve-2026-101352
- https://www.libreoffice.org/security/#cve-2026-101352
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-101352
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-101352"}.Timeline
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- CVE published
- First seen by cve.now1 day
- Record last updated
Affected versions
- The Document Foundation LibreOffice
From 26.2 · fixed in < 26.2.7; From 26.8 · fixed in < 26.8.2
Evidence 3
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Link
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-101352
Is CVE-2026-101352 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A document can carry its own keyboard shortcuts, menus and toolbars, which take effect while the document is open. In a crafted document, pressing a shortcut or choosing a menu item could run code on the user's machine without any security warning, even when the macro security settings did not allow the document's macros.Source: libreoffice.org
Which versions are affected by CVE-2026-101352?
LibreOffice: from 26.2 before < 26.2.7; from 26.8 before < 26.8.2.Source: cve.now feed data
How do I fix CVE-2026-101352?
Upgrade to a fixed version: < 26.2.7, < 26.8.2. The vendor's advisory also recommends 26.2.7 or 26.8.2 or later.Source: cve.now feed data, libreoffice.org