{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-59265 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-59265 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-59265 is a high-severity code injection vulnerability in Apache OpenOffice, published on 2 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-59265 and fix it if it is affected.\n\nWhat it is: CVE-2026-59265 is a high-severity code injection vulnerability in Apache OpenOffice, published on 2 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-59265 in the wild and no public exploit code.\n\nAffected product: Apache OpenOffice. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-59265/ (Markdown: https://insights.sbomify.com/CVE-2026-59265/index.md)","id":"CVE-2026-59265","markdown":"https://insights.sbomify.com/CVE-2026-59265/index.md","name":"CVE-2026-59265","record":{"aliases":["GHSA-55r6-rg38-gm55"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Office suite","requires_auth":"none","summary":"Attackers can execute arbitrary code by tricking users into opening malicious documents in Apache OpenOffice.","user_interaction":"required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[],"cvss":{"score":8.8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-426","name":"Untrusted Search Path"}],"description":"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\nThis issue is expected to be fixed in version 4.1.17, which is in the release candidate phase.\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 open untrusted files entirely. Once 4.1.17 is released, upgrade to that version to fix the issue.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-10-06","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-10-06T15:12:44Z","kind":"github_poc","ref":"https://github.com/HORKimhab/CVE-2026-59265","stars":0,"title":"CVE-2026-59265"}],"tier":"poc_unverified"},"has_fix":false,"headline":"Apache OpenOffice, Apache OpenOffice: Opening a malicious document can lead to system takeover","id":"CVE-2026-59265","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Privilege escalation in Pinniped","id":"CVE-2026-59269"},"packages":[],"prev":{"headline":"AFFiNE - Unauthorized Document Edit History Access via GraphQL histories Field","id":"CVE-2026-59262"},"products":["Apache OpenOffice"],"published":"2026-10-02","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-08","vendors":["Apache Software Foundation"]},"summary":"Attackers can execute arbitrary code by tricking users into opening malicious documents in Apache OpenOffice.","url":"https://insights.sbomify.com/CVE-2026-59265/"}