Home › Intelligence › Brief
VULNERABILITY BRIEF 🟠 High Vulnerability

Remote Code Execution via LibreOffice EMF+ Integer Overflow (CVE‑2026‑6045)

LibreOffice disclosed CVE‑2026‑6045, an integer‑overflow flaw in its EMF+ image parser that can lead to arbitrary code execution when a victim opens a crafted ODT file. The vulnerability underscores the need for robust vulnerability‑management controls and audit‑ready evidence of patching.

Verisq™ Intelligence · 📅 October 17, 2026 · 📰 zerodayinitiative.com
🟠
Severity
High
VU
Type
Vulnerability
🎯
Confidence
High
🏢
Affected
1 sector(s)
✅
Actions
4 recommended
📰
Source
zerodayinitiative.com

Remote Code Execution via LibreOffice EMF+ Integer Overflow (CVE‑2026‑6045)

What It Is – A newly disclosed integer‑overflow flaw in the EMF+ image parser of LibreOffice ODT files allows an attacker to execute arbitrary code on the victim’s machine. The vulnerability is tracked as CVE‑2026‑6045 and carries a CVSS 7.8 (High) rating.

Exploitability – The bug is locally exploitable after a user opens a malicious ODT file or visits a crafted web page that triggers the parser. No public exploit code is known, but the required user interaction (UI:R) makes the risk realistic for targeted phishing or drive‑by scenarios.

Affected Products – All current releases of LibreOffice (the open‑source office suite) are impacted until the vendor‑released patch is applied.

Why It Matters for Trust & Control Assurance

  • Demonstrates the need for a vulnerability‑management control that ensures timely patching of third‑party software across the enterprise.
  • Highlights the importance of continuous evidence collection (e.g., patch‑status dashboards) to prove due diligence during audits.
  • Reinforces that audit‑ready logging of software inventory and update actions is a core trust signal for buyers and regulators.

Recommended Actions

  1. Deploy the LibreOffice security update released on 2026‑10‑16 to all endpoints.
  2. Verify the installed version via automated inventory tools and document the remediation in your control evidence repository.
  3. Enable logging of file‑open events for ODT documents and monitor for anomalous activity.
  4. Incorporate this CVE into your vulnerability‑scanning schedule and risk register.

Source: Zero Day Initiative Advisory – ZDI‑26‑781

📰 Original Source
http://www.zerodayinitiative.com/advisories/ZDI-26-781/ ↗

This Verisq Intelligence Brief is an independent analysis. Read the original reporting at the link above.

Vulnerability exposure

Is this CVE in your supply chain?

Verisq matches published vulnerabilities against the software your vendors run, so you know which relationships this touches before the next review.

See vendor exposure →