A vulnerability in LibreOffice Writer allows crafted documents with content controls bound to custom XML data to write arbitrary files during export to DOCX format. This occurs because values from the document were not properly escaped, enabling file writes to any location writable by the user. The issue affects command-line conversions as well. Fixed versions prevent file writes and network usage during XSLT transformations.
A vulnerability in LibreOffice Draw's PDF import feature allows an out-of-bounds write when processing images with transparency masks. This occurs because positions from crafted images are not properly validated against the image buffer size. The flaw can lead to memory corruption. Fixed versions limit image size and validate mask pixel positions before writing.
CVE-2026-106535 is a medium severity vulnerability in libvisio, a library used by LibreOffice and other applications to import VSD and VSDX drawing files. The flaw is an out-of-bounds write triggered by a crafted VSDX file containing a malformed path within the drawing. Fixed versions handle malformed paths safely without writing outside allocated data.
CVE-2026-129306 is a vulnerability in the DMTF libspdm library where certificate validation does not properly verify the entire X.509 certificate chain. Prior to versions 3.8.3 and 4.0.0-rc2, the library validates certificates one link at a time rather than the full chain, potentially allowing an attacker to present a subordinate certificate that violates path length or name constraints. This can lead to identity impersonation under specific deployment conditions. The issue is fixed in libspdm versions 3.8.3 and 4.0.0-rc2.
mail-parser is a tool that parses emails by enhancing the Python standard library and extracting message details into a comprehensive object. From 4.6.0 until 4.6.3, write_attachments() calls _safe_attachment_filename() and write_sample() without isolating failures for individual attacker-controlled MIME parts. An RFC 2231 filename containing a NUL, a basename exceeding NAME_MAX, or an undecodable base64 payload can raise ValueError, OSError, or binascii.Error and abort the entire save loop. Later attachments remain unwritten; when a caller catches only MailParserError, the failure is not surfaced through the expected library-exception path. If a downstream scanner or sandbox reads only the extraction directory, a payload after the crafted part can be missed even though it remains in the delivered message, and the aborted batch also causes availability loss. This issue is fixed in version 4.6.3.
mail-parser is a tool that parses emails by enhancing the Python standard library and extracting message details into a comprehensive object. From 3.7.0 until 4.6.3, receiveds_format() in src/mailparser/utils.py catches only TypeError and ValueError while converting the trailing date of an attacker-controlled Received header. An out-of-range year can cause calendar.timegm() to raise OverflowError, and a sufficiently large timezone offset can cause datetime.fromtimestamp() to raise OSError. These exceptions are outside the MailParserError hierarchy, so one crafted header can abort the entire message parse through every parse_from_* entry point and may drop a queued batch. This issue is fixed in version 4.6.3.
mail-parser is a tool that parses emails by enhancing the Python standard library and extracting message details into a comprehensive object. Prior to 4.6.2, multiple message-processing behaviors can raise exceptions or silently lose content. Headers colliding with methods such as Parse, Message, and Write_Attachments can place bound method objects into parsed output and raise TypeError when a caller requests JSON serialization such as mail_json. When byte input is parsed through parse_from_bytes(), an 8-bit header value returned as email.header.Header can likewise raise TypeError when an X_raw accessor passes the value to json.dumps; both exceptions are outside the MailParserError hierarchy. Separately, rewritten names such as Subject_json and X_Spam_Flag can be substituted or disappear from mail, headers, and JSON output while has_defects remains false, and a headerless message can be treated as falsy before parser state is initialized, causing body and attachment properties to return empty values without an error signal. These behaviors can abort message processing or hide malicious indicators from downstream scanners. This issue is fixed in version 4.6.2.
LibreOffice documents can include Basic macro libraries stored in a compiled form. A vulnerability exists due to an out-of-bounds write when reading these compiled libraries, caused by unchecked string positions and improper type validation. Fixed versions include checks that prevent loading malformed libraries and ignore incorrect types.
LibreOffice Writer versions listed can open HTML documents that may contain macros bound to document-wide events such as opening or closing. These macros were not properly checked by the macro security mechanism, allowing them to run regardless of the macro security level. Fixed versions enforce macro security settings on these macros like any other macro in the document.
LibreOffice documents can embed user interface customizations such as keyboard shortcuts, menus, and toolbars that become active when the document is open. These customizations could bind commands that run macros or scripts even if macro security settings disallow macros, enabling code execution without warning when a user activates them. Fixed versions treat these customizations like other macro content, only preserving macro and script commands if macros are allowed by the document's security settings.
A vulnerability in LibreOffice Base allows macros bound to document events, such as opening or closing, to run without respecting the macro security settings. This means that opening or converting a crafted database document could execute macros and arbitrary commands. The issue is fixed in later versions where such macros follow the macro security settings like other document macros.
A vulnerability in LibreOffice allows out-of-bounds reads when importing EMF, EMF+, and WMF images embedded in documents. This occurs because sizes, counts, and offsets from crafted images were not properly validated against the actual data. Fixed versions perform these checks and ignore records that fail validation.
CVE-2026-18563 is a vulnerability in LibreOffice related to the handling of embedded fonts when exporting documents to PDF. Specifically, an out-of-bounds write occurs during the interpretation of the charstring program of a crafted Compact Font Format (CFF) font due to unchecked indexes and ranges. This flaw can lead to memory corruption. Fixed versions include checks on these indexes and ranges, preventing conversion of fonts that fail validation.
LibreOffice Calc can open spreadsheets in the DIF format, and text files such as CSV in the UTF-16 encoding. Both are read one line at a time. An out-of-bounds read existed when a line of a crafted file was read, because the length of the line could be miscalculated, so memory beyond the line could be copied into the imported document. In fixed versions each line is read up to its limit and no further.
LibreOffice checks the digital signatures of a PDF document when the document is opened, and shows whether each signature is valid. An out-of-bounds write existed when a signature was checked, because the parts of the file that a crafted signature claims to cover were not checked against the size of the file. In fixed versions a signature that claims to cover anything outside the file is reported as not valid.