Answer in brief
CVE-2026-59265 records a Unknown severity vulnerability in Apache OpenOffice, Apache OpenOffice: Opening a malicious document can lead to system takeover. The current sources do not mark it as known exploited. The current feed maps Apache Software Foundation/Apache OpenOffice (generic), Apache Software Foundation/Apache OpenOffice (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Apache Software Foundation/Apache OpenOffice (generic), Apache Software Foundation/Apache OpenOffice (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Apache Software Foundation/Apache OpenOfficegeneric | >=0 <=4.1.16 | Not reported |
| Apache Software Foundation/Apache OpenOfficegeneric | >=0 <95923fd437e06edd38a4f0e139a27c755a6f3ba6 || >=0 <181421139242694b309751fb666406eddc203c50 | 95923fd437e06edd38a4f0e139a27c755a6f3ba6, 181421139242694b309751fb666406eddc203c50 |
Published upstream
Oct 2, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 2, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 2, 2026
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.
Quoted source text, attributed separately from HOL analysis.