Heap buffer overflow via change type confusion
Published Jun 15, 2026 · Updated Jun 15, 2026
Type confusion in LibreOffice Calc before 26.2.4 allows local users to corrupt heap memory by opening a crafted spreadsheet. The tracked-changes importer reuses a duplicate change identifier, casts the existing change object to a different, larger type, and writes beyond its allocation. Triggering the flaw requires passive interaction with attacker-controlled tracked-change records and can crash Calc or corrupt spreadsheet data held in process memory.
Summary
What happened
Type confusion in LibreOffice Calc before 26.2.4 allows local users to corrupt heap memory by opening a crafted spreadsheet. The tracked-changes importer reuses a duplicate change identifier, casts the existing change object to a different, larger type, and writes beyond its allocation. Triggering the flaw requires passive interaction with attacker-controlled tracked-change records and can crash Calc or corrupt spreadsheet data held in process memory.
The record
- CVE
- CVE-2026-8358
- Published
- Jun 15, 2026
- Updated
- Jun 15, 2026
- Vendor
- The Document Foundation
- Product
- LibreOffice
- Classifications
- CWE-843, CWE-787, CAPEC-44, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 15, 2026CVE publishedPublication date reported by the CVE source.
- Jun 15, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=26.2 << 26.2.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo