CVE-2026-18563 in LibreOffice
Summary
by MITRE • 11/16/2026
LibreOffice supports fonts embedded in documents. When a document is exported to PDF, the fonts it uses are embedded in the PDF, and a font in CFF (Compact Font Format) is converted to another font format on the way. An out-of-bounds write existed when the charstring program of a crafted font was interpreted, because some indexes and ranges taken from the font were not checked against the size of the data they refer to. In fixed versions these indexes and ranges are checked, and a font that fails the checks is not converted.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Analysis
by VulDB Data Team • 11/16/2026
The vulnerability identified in LibreOffice pertains to the handling of embedded fonts during the document export process to PDF format. Specifically, this issue affects documents containing CFF (Compact Font Format) fonts which undergo conversion to an alternative font structure as part of the rendering pipeline for PDF generation. The core technical flaw lies within the interpreter responsible for processing charstring programs associated with these fonts. When a crafted or maliciously constructed font file is processed, the software fails to validate critical indexes and range values against the actual size of the underlying data buffers. This lack of boundary checking allows an attacker to craft a font where specific indices point beyond the allocated memory space, leading directly to an out-of-bounds write condition during execution.
From a technical perspective, this flaw represents a classic buffer overflow vulnerability categorized under CWE-787: Out-of-Bounds Write in the Common Weakness Enumeration standard. The absence of rigorous validation for array bounds and data segment sizes means that arbitrary memory locations can be overwritten when the charstring program is interpreted. This type of error typically occurs because the application trusts input data from external sources, such as embedded fonts within a document, without performing sufficient integrity checks on structural elements like glyph indices or path commands. The consequence of this unchecked access is potentially severe, allowing for arbitrary code execution if an attacker can control the content written to memory and manipulate subsequent program flow through stack smashing or heap corruption techniques.
The operational impact of this vulnerability extends beyond simple application crashes. While a denial-of-service condition resulting from a crash is a likely immediate outcome, the primary risk involves remote code execution. An adversary could distribute a malicious document containing the crafted CFF font via email or file sharing services. Upon opening and exporting the document to PDF within LibreOffice, the vulnerable component would execute the malformed charstring program, triggering the out-of-bounds write. This aligns with ATT&CK technique T1203: Exploitation for Client Execution, where attackers exploit vulnerabilities in client software to gain initial access or persistence on a target system by leveraging trusted applications like office suites as vectors for malware delivery.
Mitigation strategies primarily involve updating LibreOffice to the fixed versions that implement proper bounds checking logic. In these patched releases, indexes and ranges extracted from font data are validated against the size of the referenced data structures before processing occurs. If any index or range exceeds valid limits, the conversion process is halted, preventing the execution of potentially malicious code paths. Users should ensure their software is up to date with the latest security patches provided by LibreOffice maintainers. Additionally, organizations can enforce policies that restrict the opening of documents from untrusted sources and enable macro protection features to reduce the attack surface associated with document-based exploits. Regular auditing of third-party components used in office productivity suites remains essential for maintaining robust defense-in-depth against such input validation failures.