Apache Software Foundation Apache OpenOffice
Apache OpenOffice, Apache OpenOffice: Opening a malicious document can lead to system takeover
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- <= 4.1.16
- < 95923fd437e06edd38a4f0e139a27c755a6f3ba6
- < 181421139242694b309751fb666406eddc203c50
Fixed in 95923fd437e06edd38a4f0e139a27c755a6f3ba6, 181421139242694b309751fb666406eddc203c50
Mitigation
Upgrade Apache OpenOffice to 95923fd437e06edd38a4f0e139a27c755a6f3ba6 or 181421139242694b309751fb666406eddc203c50 or later.
References
Timeline
Days relative to CVE publicationFirst public PoC 3.9 days after publication; not in CISA KEV. First PoC: HORKimhab/CVE-2026-59265 (created 6 Oct 2026, found by us: backfilled).
PoC repositories
Found on GitHub.1 PoCs
PoCs 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| HORKimhab/CVE-2026-59265 | 6 Oct 2026 +3.9 d | 0 | PoC
Flags · score 25
Below the suspicion threshold (50); does not change the assessment. |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.