Skip to content
VulniPulse
Advisory severityUnratedApache Software Foundation Updated

Advisory [CVE-2026-59265] Apache OpenOffice, Apache OpenOffice: Opening a malicious document can lead to system takeover

This security Apache Software Foundation advisory covers CVE-2026-59265 affecting Apache OpenOffice.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-59265 Source published Source updated

VulniPulse record published Record updated

Affected products & platforms
Apache Software FoundationUnclassified
Open source advisory

Android app · Google Play

Monitor future Apache Software Foundation CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

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
  • Apache OpenOffice through 4.1.16
  • Apache OpenOffice before 95923fd437e06edd38a4f0e139a27c755a6f3ba6
  • Apache OpenOffice before 181421139242694b309751fb666406eddc203c50

Official advisory · medium-confidence parse· fetched 4 days ago·verify at source

Fixed versions
  • 95923fd437e06edd38a4f0e139a27c755a6f3ba6
  • 181421139242694b309751fb666406eddc203c50

Official advisory · medium-confidence parse· fetched 4 days ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • Once 4.1.17 is released, upgrade to that version to fix the issue.

Official advisory · medium-confidence parse· fetched 4 days ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.