Executive Summary
In October 2026, critical vulnerabilities were discovered in LibreOffice (CVE-2026-63277) and Apache OpenOffice (CVE-2026-59265) that allow attackers to execute arbitrary code through malicious spreadsheets without triggering macro warnings. The attack exploits database range functionality combined with JDBC drivers to automatically download and execute malicious Java code when a crafted spreadsheet is opened, requiring only that Java support is enabled. LibreOffice released patches on October 5, 2026 (versions 26.2.5 and 26.8.0), while Apache OpenOffice remains vulnerable with a fix expected in version 4.1.17.
This incident highlights the evolving threat landscape where attackers are finding new ways to bypass traditional security warnings and execute code through seemingly benign document features. The vulnerability demonstrates how legitimate application functionality can be chained together to create attack vectors that circumvent established security controls.
Why This Matters Now
Office document-based attacks are resurging as attackers develop new techniques to bypass macro security controls. With millions of users relying on open-source office suites and the continued vulnerability in Apache OpenOffice, organizations face immediate risk from weaponized documents that execute code without user consent.
Attack Path Analysis
Attackers deliver malicious spreadsheets that exploit CVE-2026-63277 and CVE-2026-59265 to achieve code execution through database range features and JDBC drivers without macro warnings. Upon opening, the spreadsheet downloads remote ODB files and JAR code which executes within the office application context. From the compromised endpoint, attackers can establish persistence, move laterally through network shares and remote systems, maintain command and control through the initial Java payload, exfiltrate sensitive documents and data, and potentially deploy ransomware or destructive payloads across the environment.
Kill Chain Progression
This analysis maps confirmed threat intelligence to the full cloud kill chain to show where defensive gaps would emerge as an attack progresses.
Initial Compromise
Description
Malicious LibreOffice/OpenOffice Calc spreadsheet delivered via email or web download exploits database range and JDBC driver features to execute remote Java code without macro warnings when Java support is enabled
Related CVEs
CVE-2026-63277
CVSS 8.5A vulnerability in LibreOffice allows remote code execution through malicious spreadsheets that exploit database range functionality to download and execute arbitrary Java code without macro warnings when Java support is enabled.
Affected Products:
The Document Foundation LibreOffice – < 26.2.5, < 26.8.0
Exploit Status:
proof of conceptCVE-2026-59265
CVSS 8.8A vulnerability in Apache OpenOffice allows remote code execution through malicious spreadsheets that exploit database range functionality to download and execute arbitrary Java code without macro warnings when Java support is enabled.
Affected Products:
Apache Software Foundation OpenOffice – <= 4.1.16
Exploit Status:
proof of concept
MITRE ATT&CK® Techniques
Spearphishing Attachment
Malicious File
JavaScript
Obfuscated Files or Information
Process Injection
Exploitation for Client Execution
Ingress Tool Transfer
Potential Compliance Exposure
Mapping incident impact across multiple compliance frameworks.
NIST Cybersecurity Framework 2.0 – Threat and vulnerability information is received from information sharing forums and sources
Control ID: ID.RA-07
PCI DSS 4.0 – Security vulnerabilities are identified and managed
Control ID: 6.3.1
CISA Zero Trust Maturity Model 2.0 – Application Security Controls
Control ID: Applications and Workloads - Advanced
DORA – Identification of ICT Risk
Control ID: Article 8
NIS2 Directive – Cybersecurity Risk Management Measures
Control ID: Article 21
ISO 27001:2022 – Management of technical vulnerabilities
Control ID: A.12.6.1
Sector Implications
Industry-specific impact of the vulnerabilities, including operational, regulatory, and cloud security risks.
Government Administration
Critical vulnerability in widely-used office suites enables remote code execution without macro warnings, threatening sensitive government data and operations requiring immediate patching.
Financial Services
LibreOffice/OpenOffice flaws allow attackers to execute malicious code through spreadsheets, bypassing security controls and potentially compromising financial data and regulatory compliance requirements.
Health Care / Life Sciences
Remote code execution via malicious spreadsheets poses severe HIPAA compliance risks, potentially exposing patient data through compromised office applications requiring urgent updates.
Higher Education/Acadamia
Educational institutions using open-source office suites face significant security exposure from spreadsheet-based attacks that execute code without user awareness or consent.
Sources
- LibreOffice and OpenOffice Flaws Let Malicious Spreadsheets Run Code Without Macro Warningshttps://thehackernews.com/2026/10/libreoffice-and-openoffice-flaws-let.htmlVerified
- LibreOffice Security Advisory - CVE-2026-63277https://www.libreoffice.org/security/Verified
- OSS Security Mailing List - Apache OpenOffice CVE-2026-59265https://www.openwall.com/lists/oss-security/2026/10/02/2Verified
- V12 Security Proof of Concept Repositoryhttps://github.com/v12-security/pocs/tree/main/office_jdbc_bugsVerified
Frequently Asked Questions
Cloud Native Security Fabric Mitigations and ControlsCNSF
Based on the attack progression modeled above, these are the defensive controls that would constrain each stage.
Aviatrix Zero Trust CNSF would likely constrain this LibreOffice/OpenOffice exploit attack by limiting lateral movement pathways and reducing the attacker's blast radius through network segmentation and controlled egress policies.
Control: Cloud Native Security Fabric (CNSF)
Mitigation: Cloud-native security fabric would likely limit the scope of initial Java code execution by constraining network reachability from compromised endpoints to critical cloud workloads and reducing available attack paths through application-aware segmentation policies.
Control: Zero Trust Segmentation
Mitigation: Zero trust segmentation would likely constrain privilege escalation attempts by limiting the compromised application's access to privileged network segments and reducing the scope of resources available for exploitation through identity-aware access controls.
Control: East-West Traffic Security
Mitigation: East-west traffic security would likely constrain lateral movement by blocking unauthorized inter-segment communication and reducing the attacker's ability to traverse network shares or establish remote desktop connections through granular traffic inspection and policy enforcement.
Control: Multicloud Visibility & Control
Mitigation: Multicloud visibility and control would likely limit command and control channels by constraining outbound communication paths and reducing the attacker's ability to maintain persistent connections through comprehensive traffic monitoring and policy enforcement across cloud environments.
Control: Egress Security & Policy Enforcement
Mitigation: Egress security and policy enforcement would likely constrain data exfiltration by limiting outbound data transfer paths and reducing the volume of sensitive information that could be transmitted through controlled egress points and data loss prevention policies.
Despite CNSF protections, some business disruption could still occur on initially compromised endpoints, though the blast radius would likely be significantly reduced with ransomware deployment constrained to isolated network segments rather than spreading enterprise-wide.
Impact at a Glance
Affected Business Functions
- Document Processing
- Office Productivity
- Data Management
- Business Communications
Estimated downtime: 1 days
Estimated loss: N/A
Potential exposure of any data accessible through compromised office applications, including documents, spreadsheets, and database connections. The vulnerability allows arbitrary code execution with user privileges, potentially leading to data theft or system compromise.
Recommended Actions
Key Takeaways & Next Steps
- • Deploy Cloud Firewall (ACF) with URL filtering and egress controls to block downloads of malicious ODB and JAR files from attacker-controlled servers
- • Implement Inline IPS (Suricata) to detect and block exploit traffic patterns associated with CVE-2026-63277 and CVE-2026-59265 exploitation attempts
- • Enable Egress Security & Policy Enforcement to prevent unauthorized data exfiltration and block communications to suspicious external destinations
- • Deploy Zero Trust Segmentation with least privilege policies to contain lateral movement from compromised endpoints to critical business systems
- • Activate Multicloud Visibility & Control to detect anomalous file access patterns and suspicious automation behaviors indicative of document-based attacks



