Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCraft document with malicious CFF font
-
DeliveryDeliver file to victim or conversion pipeline
-
ExploitVictim opens and exports to PDF
-
ExecutionFont subsetting overflows fixed stack buffer
-
ImpactApplication crash / memory corruption
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, write limits
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the victim to open an attacker-supplied document containing a maliciously embedded CFF font AND to trigger font subsetting - specifically by exporting the document to PDF (or any code path that subsets the embedded font). It is not remotely reachable without this action: the CVSS vector is AV:L with UI:P (user interaction/passive victim participation required) and no privileges (PR:N). Limiting factors: the attack is confined to local document processing, the primary outcome is an application crash (VA:H) rather than reliable code execution, and it only manifests when a CFF font is actually embedded and the subset/PDF-export operation runs. Server-side or batch document-to-PDF conversion services that ingest untrusted files are the highest-risk deployment mode. |
| Impact | This is a genuine but moderate-severity memory-corruption bug, not a critical priority. The vendor CVSS 4.0 vector (AV:L/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:H) correctly frames it as a locally-vectored, user-interaction-gated flaw whose dominant impact is availability (VA:H, i.e. a crash) with only limited confidentiality/integrity impact from the out-of-bounds stack write. The E:P threat metric in the supplied vector indicates proof-of-concept-level exploit maturity, but the input provides no explicit standalone POC reference, no EPSS score, and no CISA KEV entry - so exploitation status is best characterized as 'no public exploit identified' with a caveat that the vendor's own E:P suggests PoC awareness. No SSVC decision data was supplied. The signals are internally consistent: a stack buffer overflow (CWE-787) in a font-conversion routine that only runs when a victim opens a malicious document and drives PDF export is realistically a crash/DoS with speculative code-execution potential, not a mass-exploitable remote vulnerability. Treat as a normal patch-cycle item, prioritized higher for environments doing automated/server-side document-to-PDF conversion where attacker-supplied files are processed at scale. |
| Exploit ScenarioDerived | An attacker crafts an office document embedding a malicious CFF font whose glyph program emits far more Type 1 operators than the fixed conversion buffer can hold, then delivers it to a victim (email attachment, download, or an automated PDF-conversion pipeline). When the victim opens the document and exports it to PDF, LibreOffice subsets and converts the font, overflowing the stack buffer and crashing the application, with potential for memory corruption. The vendor vector's E:P marker implies proof-of-concept-level maturity, though no standalone public exploit is referenced in the supplied data. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 22, 2026
Stack buffer overflow in LibreOffice's font subsetting path can crash the application and corrupt memory when a document containing an embedded CFF font is exported to PDF. The vulnerable routine converts CFF (Compact Font Format) glyphs to Type 1 operators during subsetting and writes them into a fixed-size stack buffer without verifying remaining capacity, so a glyph that emits many operators overflows the buffer (CWE-787). Exploitation is local and requires the victim to open an attacker-supplied document and trigger the subsetting code path (typically a PDF export); the CVSS v4.0 base score is 5.4 with PR:N and UI:P, and despite a proof-of-concept maturity rating (E:P) indicating publicly available exploit code exists, there is no confirmed active exploitation (not in CISA KEV). The most likely outcome is an application crash (VA:H) with limited confidentiality and integrity impact; headless or server-side document-to-PDF conversion services that ingest untrusted files are the highest-risk deployment mode.
RemediationAI
Patch first: a vendor fix exists that adds remaining-capacity tracking so the CFF-to-Type 1 conversion stops before overflowing the buffer, so update LibreOffice to the fixed release named in the advisory at https://www.libreoffice.org/about-us/security/advisories/cve-2026-63276 (the advisory is the only authoritative source for the exact fixed version, which is not enumerated in this dataset). If immediate upgrade is not possible, the highest-value compensating control is to break the trigger condition - during PDF export, disable OpenType/font embedding in the PDF export options so the embedded CFF font is not subset and the vulnerable conversion is never invoked; the trade-off is larger or differently rendered PDFs and loss of embedded-font fidelity on systems lacking the original fonts. Treat documents from untrusted sources as hazardous: do not PDF-export them in a normal user session, and instead perform conversions in a disposable VM, container, or low-privilege sandbox with no access to valuable data. Operators of headless or server-side document-to-PDF conversion pipelines (the highest-risk deployment mode) should isolate the conversion worker, cap its privileges and resources, and monitor for crashes, since the primary observable impact is an application crash accompanying the memory corruption.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
LibreOffice embeds fonts into documents and, when exporting to PDF, performs font subsetting that may convert embedded CFF (Compact Font Format) glyph outlines into Type 1 charstring-style operators. The vulnerable conversion routine serializes those operators into a fixed-size stack buffer and previously trusted that the emitted data would always fit; a crafted glyph that produces an unusually large number of operators therefore writes past the end of that buffer, a classic stack-based out-of-bounds write (CWE-787). The flaw is reachable only through the local font-subsetting code path, not through a network-facing service by itself, and only when a CFF font is actually embedded in the document and the subset/convert operation runs. The fix does not resize the buffer but instead tracks the remaining capacity and aborts the conversion once it is exhausted, trading completeness of the conversion for memory safety. The affected component is identified by CPE cpe:2.3:a:the_document_foundation:libreoffice:*:*:*:*:*:*:*:* (vendor wildcard versioning), and the issue was reported to the vendor by the Document Foundation security process.
Know when Libreoffice gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:H/SC:N/SI:N/SA:N/E:P
Local file must be opened and exported to PDF by the victim, so AV:L and UI:R; overflow chiefly crashes the app (A:H) with limited stack-corruption C/I impact and no scope change.
AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
Primary rating from Vendor (Document Fdn.).
CVSS VectorVendor: Document Fdn.
Lifecycle Timeline
2DescriptionCVE.org
LibreOffice converts CFF fonts to Type 1 when it subsets a font, which happens when a document is exported to PDF, and CFF fonts may be embedded in documents. A stack buffer overflow existed in that conversion. The converted operators were written into a fixed size buffer with no check that they still fit, so a glyph emitting many operators wrote past the end of the buffer. In fixed versions the remaining capacity is tracked and the conversion stops when it is used up.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.
Memory corruption occurs when a program writes data beyond the boundaries of allocated memory regions or accesses memory in unintended ways, violating the integrity of the process's address space.
More in Libreoffice
View allLibreOffice is typically bundled with LibreLogo, a programmable turtle vector graphics script, which can execute arbitra
Integer underflow in LibreOffice before 4.4.5 and Apache OpenOffice before 4.1.2, when the configuration setting "Load p
LibreOffice before 4.4.6 and 5.x before 5.0.1 and Apache OpenOffice before 4.1.2 allows remote attackers to cause a deni
LibreOffice before 5.4.5 and 6.x before 6.0.1 allows remote attackers to read arbitrary files via =WEBSERVICE calls in a
In the LibreOffice 7-1 series in versions prior to 7.1.2, and in the 7-0 series in versions prior to 7.0.5, the denylist
Integer overflow in filter/source/msfilter/msdffimp.cxx in OpenOffice.org (OOo) 3.3, 3.4 Beta, and possibly earlier, and
An information disclosure vulnerability occurs when LibreOffice 6.0.3 and Apache OpenOffice Writer 4.1.5 automatically p
Apache OpenOffice before 4.1.1 allows remote attackers to execute arbitrary commands and possibly have other unspecified
Integer overflow in LibreOffice before 4.4.5 and Apache OpenOffice before 4.1.2 allows remote attackers to cause a denia
LibreOffice 4.2.4 executes unspecified VBA macros automatically, which has unspecified impact and attack vectors, possib
Redland Raptor (aka libraptor) before 2.0.7, as used by OpenOffice 3.3 and 3.4 Beta, LibreOffice before 3.4.6 and 3.5.x
LibreOffice before 2017-03-11 has an out-of-bounds write caused by a heap-based buffer overflow in the SVMConverter::Imp
Same weakness CWE-787 – Out-of-bounds Write
View allSame technique Buffer Overflow
View allVendor StatusVendor
SUSE
Severity: Important| Product | Status |
|---|---|
| SUSE Linux Enterprise Desktop 15 SP7 | Affected |
| SUSE Linux Enterprise Module for Package Hub 15 SP7 | Affected |
| SUSE Linux Enterprise Server 15 SP7 | Affected |
| SUSE Linux Enterprise Server for SAP Applications 15 SP7 | Affected |
| SUSE Linux Enterprise Workstation Extension 15 SP7 | Affected |
| SUSE Linux Enterprise Server 15 SP5 | Affected |
| SUSE Linux Enterprise Server 15 SP6 | Affected |
| SUSE Linux Enterprise Server for SAP Applications 15 SP5 | Affected |
| SUSE Linux Enterprise Server for SAP Applications 15 SP6 | Affected |
| SUSE Linux Enterprise Desktop 15 SP5 | Affected |
| SUSE Linux Enterprise Desktop 15 SP6 | Affected |
| SUSE Linux Enterprise Module for Package Hub 15 SP5 | Affected |
| SUSE Linux Enterprise Module for Package Hub 15 SP6 | Affected |
| SUSE Linux Enterprise Workstation Extension 15 SP5 | Affected |
| SUSE Linux Enterprise Workstation Extension 15 SP6 | Affected |
| openSUSE Leap 15.5 | Affected |
| openSUSE Leap 15.6 | Affected |
EUVD-2026-84356
GHSA-3xpv-4h8q-pj26
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB