CVE-2026-101352 in LibreOfficeinfo

Summary

by MITRE • 11/16/2026

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.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Analysis

by VulDB Data Team • 11/16/2026

This vulnerability represents a significant security flaw within office suite applications where document-level user interface customizations bypass standard macro execution restrictions. The core technical issue stems from how legacy or specific application versions handle embedded customization data, such as keyboard shortcuts, menu definitions, and toolbar configurations. These elements are often stored separately from the main code base of macros but share similar execution privileges when triggered by user interaction. In a compromised scenario, an attacker crafts a document containing malicious UI customizations that bind critical commands to macro or script executions. When a victim opens this file, the application loads these customizations into the active interface environment without triggering the standard security prompts associated with direct macro activation.

The operational impact is severe because it effectively neutralizes user-configured security settings designed to prevent unauthorized code execution. Even if an organization has strictly configured its software to block all macros from untrusted sources or requires explicit user consent for every script run, this flaw allows attackers to circumvent those controls entirely. By simply pressing a predefined keyboard shortcut or clicking a menu item that appears normal within the document's interface, the victim inadvertently triggers the execution of arbitrary code. This mechanism is particularly dangerous because it relies on social engineering and trust in the application's user interface rather than exploiting complex binary memory corruption issues, making detection by traditional signature-based antivirus solutions difficult until after execution has occurred.

From a classification perspective, this vulnerability aligns with CWE-94 Improper Control of Generation of Code or Script, specifically where code injection occurs through improperly sanitized input that influences the application's behavior without adequate validation. It also maps to MITRE ATT&CK techniques related to Execution via User Interaction and potentially Command Line Interface execution if the underlying scripts invoke system commands. The flaw highlights a failure in enforcing consistent security policies across different components of an office document, treating UI customization data with lower trust levels than actual macro code despite both having the potential for arbitrary code execution.

Mitigation strategies primarily involve applying vendor-provided patches that update how these customizations are processed. In fixed versions, the application treats user interface customizations identically to other macro content within the document structure. This means that any command bound in these customizations is subject to the same security checks and restrictions as standard macros. Consequently, if a user has disabled macros for untrusted documents, the malicious commands embedded in the UI customization will not execute unless the user explicitly allows all macro content for that specific file. Organizations should ensure their software environments are updated with the latest security patches and consider implementing application whitelisting or restricted mode policies to further limit script execution capabilities across all document types regardless of internal configuration nuances.

Responsible

Document Fdn.

Reservation

09/28/2026

Disclosure

11/16/2026

Moderation

accepted

CPE

ready

EPSS

0.00000

KEV

no

Activities

very low

Sources

Interested in the pricing of exploits?

See the underground prices here!