Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCraft malicious spreadsheet with duplicate change identifiers
-
DeliveryDeliver via phishing email or malicious download
-
ExploitUser opens document in LibreOffice Calc
-
ExecutionTracked-changes importer performs type confusion on duplicate change ID
-
PersistHeap buffer overflow writes past allocation boundary
-
ImpactApplication crash (VA:H) or refined exploit achieves code execution at user privilege
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Type safety enforcement
MITRE ATT&CK
1 technique across 1 tactic: Execution 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 a crafted spreadsheet document that contains a tracked-changes section with at least two records sharing the same change identifier but representing different change types - a malformed condition that does not arise in legitimately generated documents. Passive user interaction is mandatory (CVSS 4.0 UI:P): the targeted individual must be persuaded to open the file, making social engineering the primary delivery prerequisite. No attacker authentication or privilege is required (PR:N). The vulnerability is constrained to the tracked-changes import code path in LibreOffice Calc; documents without tracked changes or with validly formed change records are not affected. Exploitation does not propagate automatically across a network and cannot be triggered remotely without user action. Scope is limited to the vulnerable system with no lateral impact on subsequent systems (SC:N/SI:N/SA:N). |
| Impact | The CVSS 4.0 base score of 5.4 (Medium) reflects a local attack vector (AV:L), passive user interaction (UI:P), no required privileges (PR:N), high availability impact (VA:H), and low confidentiality and integrity impact (VC:L/VI:L). The E:P threat modifier confirms proof-of-concept exploit code exists, elevating practical risk above the base score alone - defenders should treat this as more accessible than a theoretical flaw. The attack vector being local in CVSS 4.0 terminology for a file-parsing bug means the malicious file must be processed on the local system, consistent with a user opening a delivered document; this does not imply the attacker needs physical access. No EPSS score was provided, and the absence of a KEV listing means mass exploitation is not confirmed, but the existence of a POC and a realistic delivery vector (phishing, malicious email attachment) makes targeted exploitation feasible. The high availability impact is well-supported by the heap overflow description; the low confidentiality and integrity impacts suggest that reliable memory-read or precise write primitives may not be straightforwardly achievable, though heap corruption can escalate to code execution with a refined exploit. The Medium CVSS score should not be used to de-prioritize patching in environments where users routinely open spreadsheet documents from untrusted sources. |
| Exploit ScenarioDerived | An attacker crafts a malicious LibreOffice Calc spreadsheet - in .ods or a compatible format - where the tracked-changes section assigns the same change identifier to two structurally different change record types, then delivers it via phishing email or a malicious download link. When the target user opens the file, the Calc importer processes the duplicate identifier, treats one change object as the larger type, and overwrites heap memory adjacent to the allocation; with a proof-of-concept already publicly available (E:P), a moderately skilled attacker could refine this overflow into arbitrary code execution running at the victim's user privilege level. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jun 15, 2026
Heap buffer overflow in LibreOffice Calc's tracked-changes importer allows an attacker who delivers a maliciously crafted spreadsheet to corrupt heap memory, causing high-impact availability loss and potentially enabling arbitrary code execution at the victim's privilege level. The vulnerability is triggered when a document reuses the same change identifier for two structurally different change types, causing the importer to misidentify object size and write past the allocation boundary. A proof-of-concept exists (CVSS 4.0 E:P modifier); no confirmed active exploitation (CISA KEV) has been recorded at time of analysis.
RemediationAI
Upgrade to the fixed version of LibreOffice as released by The Document Foundation; the fix enforces rejection of spreadsheet records that assign the same change identifier to two different change types. The exact patched release version is not independently confirmed from available data - consult the vendor advisory at https://www.libreoffice.org/about-us/security/advisories/cve-2026-8358 for the specific version to target. As a compensating control while awaiting patching, organizations should instruct users not to open spreadsheet files with tracked changes from untrusted or unexpected sources; disabling tracked-changes import at the macro or policy level (where supported by deployment tooling) would eliminate the vulnerable code path but may disrupt legitimate collaborative workflows. Sandboxing LibreOffice via AppArmor, Flatpak, or equivalent container isolation limits the blast radius of heap exploitation to the sandboxed process rather than the full user session. Email gateway filtering of .ods and related spreadsheet formats from external senders can reduce the most common delivery vector without impacting internal document workflows.
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 Calc, developed by The Document Foundation (CPE: cpe:2.3:a:the_document_foundation:libreoffice:*:*:*:*:*:*:*:*), implements a tracked-changes import subsystem that parses and reconstructs collaborative edit history from spreadsheet files. The root cause is CWE-843 (Access of Resource Using Incompatible Type, commonly called type confusion): the importer uses the change identifier as a key to look up or dispatch change objects, but when a document presents the same identifier for two different change kinds, the importer resolves the object as the wrong type - one that is structurally larger - and proceeds to write fields into memory beyond the actual allocation boundary. This constitutes a classic heap buffer overflow driven by type confusion, a particularly dangerous class because the write target and size are attacker-influenced. The CPE wildcard version range indicates all LibreOffice versions prior to the fix are affected; the fix enforces rejection of any record carrying a duplicate change identifier.
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
File must be opened locally (AV:L), user interaction is required to open the document (UI:R), no attacker privileges needed (PR:N), scope unchanged, availability impact is high with limited memory-leak or write primitives confirmed (C:L/I:L).
AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:H
Primary rating from Vendor (Document Fdn.).
CVSS VectorVendor: Document Fdn.
Lifecycle Timeline
2DescriptionCVE.org
LibreOffice Calc can import tracked changes from a spreadsheet document. A heap buffer overflow existed when a document reused the same change identifier for two different kinds of change. The importer then treated one change object as a different, larger type and wrote past the end of its allocation. In fixed versions records with a duplicate identifier are rejected.
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 technique Buffer Overflow
View allVendor StatusVendor
SUSE
Severity: Moderate| 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 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 Server for SAP Applications 15 SP5 | 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-36740
GHSA-gpc5-jgqj-xp2q
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB