CVE-2026-59265

Apache OpenOffice, Apache OpenOffice: Opening a malicious document can lead to system takeover

Published Oct 2, 2026 CVSS 3.1 · 8.8 High EPSS < 1% KEV · Not listed
Description
A code execution issue in the Java integration in Apache OpenOffice v4.1.16 and earlier allows a crafted untrusted document to trigger executing arbitrary (even remote) code when opened by the user.



This issue is expected to be fixed in version 4.1.17, which is in the release candidate phase.



Until then, users can mitigate this issue by disabling Java runtime integration in the Preferences dialog. This prevents the attack. If this is not possible, or as an extra precaution, you can avoid opening open untrusted files entirely. Once 4.1.17 is released, upgrade to that version to fix the issue.

Analysis

AI-generated

Technical impact

A crafted untrusted document exploits a flaw in Apache OpenOffice's Java integration, allowing an attacker to execute arbitrary local or remote code when the document is opened. This can result in complete system takeover for the user who opens the file, as the code runs with the same privileges as the user. The weakness corresponds to CWE-426, which concerns executing untrusted code from a document.

Affected Systems

Apache Software Foundation's Apache OpenOffice, versions 4.1.16 and earlier, are affected. The issue is intended to be fixed in version 4.1.17, currently in release candidate status.

Risk and Exploitability

The vulnerability can be exploited when a user opens a malicious document; based on the description, the likely attack vector is local and requires user interaction to open the file, but this is inferred rather than explicitly stated. An EPSS score of < 1% indicates a very low but non‑zero exploitation probability, and the vulnerability is not listed in CISA's KEV catalog, suggesting no known mass exploitation yet. Despite the lack of exploitation metrics, the potential for remote code execution indicates a high severity. Until the fixed release is available, the greatest risk is for users who open untrusted documents with Java integration enabled.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Apache OpenOffice to version 4.1.17 to apply the fixed code.
  • Disable Java runtime integration via the Preferences dialog to prevent the vulnerability from being exploitable if an upgrade is not immediately possible.
  • Avoid opening any untrusted documents until the upgrade is performed or execute them in a sandboxed environment.

Generated by OpenCVE AI on October 7, 2026 at 07:00 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics cvssV3_1

{'score': 8.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H'}

ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Apache
Apache openoffice
Vendors & Products Apache
Apache openoffice
Type Values Removed Values Added
Description A code execution issue in the Java integration in Apache OpenOffice v4.1.16 and earlier allows a crafted untrusted document to trigger executing arbitrary (even remote) code when opened by the user. This issue is expected to be fixed in version 4.1.17, which is in the release candidate phase. Until then, users can mitigate this issue by disabling Java runtime integration in the Preferences dialog. This prevents the attack. If this is not possible, or as an extra precaution, you can avoid opening open untrusted files entirely. Once 4.1.17 is released, upgrade to that version to fix the issue.
Title Apache OpenOffice, Apache OpenOffice: Opening a malicious document can lead to system takeover
Weaknesses CWE-426
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
apache
Published
Updated
Oct 8, 2026, 3:12 AM
Reserved
Jul 4, 2026, 3:35 PM
Status
Deferred
Published
Oct 2, 2026, 6:17 PM
Modified
Oct 8, 2026, 4:17 AM