CVE-2026-59265 (GCVE-0-2026-59265)
Vulnerability from cvelistv5 – Published: 2026-10-02 17:34 – Updated: 2026-10-02 21:07
VLAI
EPSS
VEX
Title
Apache OpenOffice, Apache OpenOffice: Opening a malicious document can lead to system takeover
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.
Severity
No CVSS data available.
CWE
- CWE-426 - Untrusted Search Path
Assigner
References
4 references
Impacted products
2 products
| Vendor | Product | Version | CPE status | |
|---|---|---|---|---|
| Apache Software Foundation | Apache OpenOffice |
Affected:
0 , ≤ 4.1.16
(semver)
|
guessed | |
| Apache Software Foundation | Apache OpenOffice |
Affected:
0 , < 95923fd437e06edd38a4f0e139a27c755a6f3ba6
(git)
Affected: 0 , < 181421139242694b309751fb666406eddc203c50 (git) |
guessed |
{
"containers": {
"adp": [
{
"providerMetadata": {
"dateUpdated": "2026-10-02T21:07:25.674Z",
"orgId": "af854a3a-2127-422b-91ae-364da2661108",
"shortName": "CVE"
},
"references": [
{
"url": "http://www.openwall.com/lists/oss-security/2026/10/02/2"
}
],
"title": "CVE Program Container"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Apache OpenOffice",
"vendor": "Apache Software Foundation",
"versions": [
{
"lessThanOrEqual": "4.1.16",
"status": "affected",
"version": "0",
"versionType": "semver"
}
]
},
{
"defaultStatus": "unaffected",
"product": "Apache OpenOffice",
"repo": "https://gitbox.apache.org/repos/asf/openoffice.git",
"vendor": "Apache Software Foundation",
"versions": [
{
"lessThan": "95923fd437e06edd38a4f0e139a27c755a6f3ba6",
"status": "affected",
"version": "0",
"versionType": "git"
},
{
"lessThan": "181421139242694b309751fb666406eddc203c50",
"status": "affected",
"version": "0",
"versionType": "git"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "finder",
"value": "Thomas Rinsma and Edoardo Geraci from Codean Labs"
},
{
"lang": "en",
"type": "finder",
"value": "Rick de Jager of the V12 security team"
}
],
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cp\u003eA 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.\u003c/p\u003e\u003cp\u003eThis issue is expected to be fixed in version 4.1.17, which is in the release candidate phase.\u003c/p\u003e\u003cp\u003eUntil 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\u0026nbsp;open untrusted files entirely.\u0026nbsp;Once 4.1.17 is released, upgrade to that version to fix the issue.\u003c/p\u003e"
}
],
"value": "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.\n\n\n\nThis issue is expected to be fixed in version 4.1.17, which is in the release candidate phase.\n\n\n\nUntil 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\u00a0open untrusted files entirely.\u00a0Once 4.1.17 is released, upgrade to that version to fix the issue."
}
],
"metrics": [
{
"other": {
"content": {
"text": "critical"
},
"type": "Textual description of severity"
},
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-426",
"description": "CWE-426: Untrusted Search Path",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-10-02T18:01:31.525Z",
"orgId": "f0158376-9dc2-43b6-827c-5f631a4d8d09",
"shortName": "apache"
},
"references": [
{
"tags": [
"patch"
],
"url": "https://github.com/apache/openoffice/commit/c699bed3f75e79bd64ddec9dec49f9e210eed281.patch"
},
{
"tags": [
"patch"
],
"url": "https://github.com/apache/openoffice/commit/95923fd437e06edd38a4f0e139a27c755a6f3ba6.patch"
},
{
"tags": [
"vendor-advisory"
],
"url": "https://lists.apache.org/thread.html/svfdc1jtpqlw7mo6lgg9fthcmf754pl5"
}
],
"source": {
"discovery": "EXTERNAL"
},
"title": "Apache OpenOffice, Apache OpenOffice: Opening a malicious document can lead to system takeover",
"x_generator": {
"engine": "Vulnogram 1.0.3"
}
}
},
"cveMetadata": {
"assignerOrgId": "f0158376-9dc2-43b6-827c-5f631a4d8d09",
"assignerShortName": "apache",
"cveId": "CVE-2026-59265",
"datePublished": "2026-10-02T17:34:06.937Z",
"dateReserved": "2026-07-04T15:35:39.146Z",
"dateUpdated": "2026-10-02T21:07:25.674Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Apache OpenOffice",
"vendor": "Apache Software Foundation",
"versions": [
{
"lessThanOrEqual": "4.1.16",
"status": "affected",
"version": "0",
"versionType": "semver"
}
]
},
{
"defaultStatus": "unaffected",
"product": "Apache OpenOffice",
"repo": "https://gitbox.apache.org/repos/asf/openoffice.git",
"vendor": "Apache Software Foundation",
"versions": [
{
"lessThan": "95923fd437e06edd38a4f0e139a27c755a6f3ba6",
"status": "affected",
"version": "0",
"versionType": "git"
},
{
"lessThan": "181421139242694b309751fb666406eddc203c50",
"status": "affected",
"version": "0",
"versionType": "git"
}
]
}
],
"source": "security@apache.org"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "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.\n\n\n\nThis issue is expected to be fixed in version 4.1.17, which is in the release candidate phase.\n\n\n\nUntil 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\u00a0open untrusted files entirely.\u00a0Once 4.1.17 is released, upgrade to that version to fix the issue."
}
],
"id": "CVE-2026-59265",
"lastModified": "2026-10-02T18:33:20.487",
"metrics": {},
"published": "2026-10-02T18:17:03.917",
"references": [
{
"source": "security@apache.org",
"url": "https://github.com/apache/openoffice/commit/95923fd437e06edd38a4f0e139a27c755a6f3ba6.patch"
},
{
"source": "security@apache.org",
"url": "https://github.com/apache/openoffice/commit/c699bed3f75e79bd64ddec9dec49f9e210eed281.patch"
},
{
"source": "security@apache.org",
"url": "https://lists.apache.org/thread.html/svfdc1jtpqlw7mo6lgg9fthcmf754pl5"
}
],
"sourceIdentifier": "security@apache.org",
"vulnStatus": "Deferred",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "CWE-426"
}
],
"source": "security@apache.org",
"type": "Primary"
}
]
}
}
}
}
Loading…
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Loading…
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.
Loading…