Skip to main content
VulnerabilityPublished Updated

CVE-2026-59265: Apache OpenOffice · Code Execution Issue

Affects openofficeSource GCVE Database

0
Compare
Authoritative record:CVE-2026-59265· High 8.8

Not known to be exploited · CVSS 8.8 High : upgrade to 4.1.17 soon.

Data as of 16 Nov 2026, 20:25 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 48% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.1.17
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Upgrade org.apache.openoffice/openoffice to 4.1.17.

Affected software

ProductAffectedFixed in
Mavenorg.apache.openoffice/openofficepkg:maven/org.apache.openoffice/openofficeOther threatsAffected
  • <4.1.17
Fixed in
  • 4.1.17

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in Apache OpenOffice version 4.1.17, currently in release candidate status. Users should upgrade to 4.1.17 once it is officially released. Until then, users can mitigate the vulnerability by disabling Java runtime integration in the Preferences dialog of Apache OpenOffice. Additionally, avoiding opening untrusted documents reduces risk.

Description

A code execution vulnerability exists in the Java integration of Apache OpenOffice versions 4.1.16 and earlier. This flaw allows a crafted untrusted document to execute arbitrary code, potentially including remote code execution, when opened by a user. The issue is addressed in version 4.1.17, currently in release candidate status. Users can mitigate the risk by disabling Java runtime integration or avoiding opening untrusted files until the update is applied.

References

Community reviews

Loading reviews…