Quick answers
- Is CVE-2026-59263 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-59263 being exploited in the wild.
- How severe is CVE-2026-59263?
- Informational severity, published 4 November 2026.
- Which products and versions are affected?
- Apache OpenOffice 4.1.16 and earlier.
- Is there a fix for CVE-2026-59263?
- Yes: fixed in 4.1.17. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-59263 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-59263?
- 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
Technical details
The vulnerability allows a manipulated document to cause OpenOffice to display substitute content instead of the actual document content, effectively deceiving the user. The attack requires user interaction (opening the corrupt document) and affects OpenOffice versions 4.1.16 and earlier. The issue is fixed in version 4.1.17.
Affected products
- Apache OpenOffice 4.1.16 and earlier
Timeline
- 2026-11-04: disclosed