{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-59489 exists.","fix":"No fix has been published for CVE-2025-59489 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-59489 is a high-severity code injection vulnerability in Unity3D Unity Editor, published on 3 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-59489 and fix it if it is affected.\n\nWhat it is: CVE-2025-59489 is a high-severity code injection vulnerability in Unity3D Unity Editor, published on 3 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-59489 exists.\n\nAffected product: Unity3D Unity Editor. 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-2025-59489/ (Markdown: https://insights.sbomify.com/CVE-2025-59489/index.md)","id":"CVE-2025-59489","markdown":"https://insights.sbomify.com/CVE-2025-59489/index.md","name":"CVE-2025-59489","record":{"aliases":["GHSA-427p-ppg4-cg5q"],"analysis":{"component_type":"developer_tool","fix_type":"patch","impacts":["code_execution","data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Unity game engine","requires_auth":"none","summary":"Attackers can execute arbitrary code and steal data by exploiting argument injection in Unity Runtime, requiring developers to rebuild affected applications.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"editor","vendor":"unity"}],"cvss":{"score":7.4,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-426","name":"Untrusted Search Path"},{"id":"CWE-88","name":"Improper Neutralization of Argument Delimiters in a Command"}],"description":"Unity Runtime before 2025-10-02 on Android, Windows, macOS, and Linux allows argument injection that can result in loading of library code from an unintended location. If an application was built with a version of Unity Editor that had the vulnerable Unity Runtime code, then an adversary may be able to execute code on, and exfiltrate confidential information from, the machine on which that application is running. NOTE: product status is provided for Unity Editor because that is the information available from the Supplier. However, updating Unity Editor typically does not address the effects of the vulnerability; instead, it is necessary to rebuild and redeploy all affected applications.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2025-10-06","github_poc":2,"max_poc_stars":39,"metasploit":0,"nuclei":0,"refs":[{"date":"2025-10-06T02:20:10Z","kind":"github_poc","ref":"https://github.com/GithubKillsMyOpsec/CVE-2025-59489-POC","stars":39,"title":"Proof Of Concept For CVE-2025-59489. Affects unity games running on Android. "},{"date":"2025-10-11T11:50:17Z","kind":"github_poc","ref":"https://github.com/taptap/cve-2025-59489","stars":15,"title":"CVE-2025-59489 Unity Vulnerability Checker"}],"tier":"weaponised"},"has_fix":null,"headline":"Code injection in Unity Editor","id":"CVE-2025-59489","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2025-59491"},"packages":[],"prev":{"headline":"Heap-based Buffer Overflow Vulnerability in TP-Link Archer AX53","id":"CVE-2025-59487"},"products":["Unity Editor"],"published":"2025-10-03","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-10-03","vendors":["Unity3D"]},"summary":"Attackers can execute arbitrary code and steal data by exploiting argument injection in Unity Runtime, requiring developers to rebuild affected applications.","url":"https://insights.sbomify.com/CVE-2025-59489/"}