CVE-2026-59265
A code execution issue in the Java integration in Apache OpenOffice v4.1.16 and earlier allows a…
- Risk score
- 65/100
- CVSS
- 8.8 v3.1
- Exploit chance (30 days)
- 0.4%
- Published
- 2 Oct 2026
Open in the live forecast Today's forecast
What to know
- What it is
- 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 mit…
- Affected
- See advisory
- Fix
- Upgrade the product to 4.1.17 or later.
- Exploitation
- No known exploitation
Why it is Amber
- CVSS 8.8 high
- Remotely exploitable without logging in
References
- https://github.com/apache/openoffice/commit/95923fd437e06edd38a4f0e139a27c755a6f3ba6.patch
- https://github.com/apache/openoffice/commit/c699bed3f75e79bd64ddec9dec49f9e210eed281.patch
- https://lists.apache.org/thread.html/svfdc1jtpqlw7mo6lgg9fthcmf754pl5
- http://www.openwall.com/lists/oss-security/2026/10/02/2
- http://www.openwall.com/lists/oss-security/2026/10/08/7
Original 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.
Last activity 2 Oct 2026. Patch Forecast updates every hour.