Quick answers
- Is CVE-2026-59265 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-59265 being exploited in the wild.
- How severe is CVE-2026-59265?
- Informational severity, published 2 October 2026.
- Which products and versions are affected?
- Apache OpenOffice 4.1.16 and earlier.
- Is there a fix for CVE-2026-59265?
- Yes: fixed in 4.1.17. Until then: Disable Java runtime integration in the Preferences dialog, or avoid opening untrusted files until the patch is available. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-59265 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-59265?
- Check whether you run Apache OpenOffice at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 4.1.17
Disable Java runtime integration in the Preferences dialog, or avoid opening untrusted files until the patch is available.
Technical details
A code execution vulnerability exists in the Java classpath integration of Apache OpenOffice, where non-local URL schemes could be added to the Java classpath through a crafted untrusted document. The vulnerability is in the classpath.cxx component which validates URLs before passing them to the JVM; insufficient validation allows remote code execution when the document is opened by a user. A fix restricts classpath entries to local file: and jrt: schemes, blocking remote class loading.
Affected products
- Apache OpenOffice 4.1.16 and earlier
Timeline
- 2026-10-02: disclosed