Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCraft WMF text record with short advance array
-
DeliveryDeliver malicious document to victim
-
ExploitVictim opens file in LibreOffice
-
ExecutionText rendering walks advance array past end
-
PersistHeap buffer overflow
-
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 | Requires the victim to open, in LibreOffice, a document or graphic that embeds a malicious WMF image containing a text record with its own character advance widths where the advance-value count is smaller than the text length. Exploitation is LIMITED by: local attack vector (AV:L) - the file must be delivered to and opened by the victim; mandatory user interaction (UI:P) - no drive-by/remote-unauthenticated path; and the crash-dominant impact profile (confidentiality/integrity Low, availability High), which bounds realistic outcomes to denial of service rather than reliable code execution. No special LibreOffice configuration is needed - WMF import is a default-enabled feature. |
| Impact | This is a low-real-priority memory-corruption bug despite a MEDIUM CVSS of 5.4. The vendor CVSS 4.0 vector (AV:L/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:H) is crash-dominant: only availability is High while confidentiality and integrity are Low, consistent with a heap out-of-bounds walk of an advance-width array that typically corrupts adjacent heap data and crashes rather than yielding attacker-controlled code execution. Exploitation is not remote-automatable - it is local (AV:L) and requires the victim to open a malicious file (UI:P/E:P is Proof-of-Concept maturity, not active exploitation). No EPSS score, no CISA KEV listing, and no public exploit are provided, so exploitation status is 'no public exploit identified at time of analysis.' The signals are internally consistent (local + user-interaction + crash-dominant impact = opportunistic, not wormable). One note: the CVSS 4.0 E:P (proof-of-concept exploit maturity) metric is present but no POC artifact is referenced in the single LibreOffice advisory - verify with vendor whether a POC actually exists, as this is the only weak divergence in the data. |
| Exploit ScenarioDerived | An attacker crafts a document (or standalone WMF graphic) embedding a WMF text record whose declared count of character advance widths is smaller than the length of the text to be drawn, and delivers it to a victim (email attachment, download). When the victim opens the file in LibreOffice, rendering the text walks the advance array by character position and reads/writes past its end, corrupting the heap and typically crashing the application. No public exploit is identified; the vendor CVSS marks exploit maturity as proof-of-concept. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 22, 2026
Heap buffer overflow in LibreOffice's WMF graphics import path affects documents embedding a crafted Windows Metafile, allowing a local attacker to corrupt memory when the victim opens the file. The flaw arises in a text record that carries its own character advance widths, where the count of advance values and the text length are read independently and need not agree, so rendering walks the advance array past its end when the array is shorter than the text. No public exploit code has been identified at time of analysis, and the impact profile is crash-dominant (confidentiality and integrity Low, availability High), making realistic outcomes denial of service rather than reliable code execution. EPSS is not provided, but exploitation requires the victim to open a malicious document (AV:L, UI:P), so real-world priority is assessed as low despite the MEDIUM CVSS of 5.4.
RemediationAI
Apply the vendor fix for CVE-2026-63272 from The Document Foundation; the advisory reference is https://www.libreoffice.org/about-us/security/advisories/cve-2026-63272, and per the advisory data an exact patched version is not enumerated in the provided input, so Patch status should be treated as 'Patch available per vendor advisory' and the concrete fixed release confirmed with the vendor or distribution before upgrading. Because WMF import is enabled by default and is the vulnerable surface, document-handling workflows should be hardened in the interim: restrict LibreOffice's processing of untrusted files to sandboxed or disposable environments (for example a container or VM with no sensitive data), and consider blocking or stripping WMF content at mail and web gateways so that such images never reach the importer - the trade-off is that legitimate legacy documents containing WMF graphics will render without their embedded images or be rejected. Headless conversion services (e.g., document-to-PDF pipelines) should run with least privilege and resource limits to contain any crash, and users should be trained not to open unexpected documents from untrusted sources, since exploitation requires the victim to open the crafted file. No public exploit code has been identified at time of analysis, so compensating controls can be prioritized rather than emergency patching.
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
WMF (Windows Metafile) is a legacy vector graphics format that LibreOffice can import, including WMF images embedded inside documents and graphics. During import, records are parsed and text-drawing records may carry an explicit array of per-character advance widths. The importer reads the number of advance values and the length of the text as two separate fields from the file and, in vulnerable versions, does not validate that they agree. When the advance array is shorter than the text, the renderer indexes the array by character position and reads past its end, producing a heap buffer overflow (CWE-787, out-of-bounds write). Fixed versions detect this inconsistency and ignore an advance array that is shorter than the text it accompanies. The root cause is a missing consistency check on attacker-controlled length fields in a parsing routine, a classic memory-safety weakness in file-format importers. The affected product is The Document Foundation's LibreOffice (CPE: cpe:2.3:a:the_document_foundation:libreoffice:*:*:*:*:*:*:*:*); the assessed vector is CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:H, consistent with the published CVSS 4.0 base of 5.4 (AV:L/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:H) and the E:P exploitability metric - note that PR:N/UI:R-UI:P reflects the file-open requirement rather than authentication.
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 by the victim (AV:L, UI:R, PR:N); heap OOB is crash-dominant so A:H with only C:L/I:L, 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 can import WMF graphics, which may be embedded in documents. A heap buffer overflow existed when importing a text record that carries its own character advance widths. The count of advance values and the length of the text were read separately from the file and were not required to agree, so drawing the text walked the advance array by character position and ran past its end when the array was the shorter of the two. In fixed versions an advance array shorter than its text is ignored.
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-84352
GHSA-c374-v965-jr6c
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB