# CVE-2025-59489: Code injection in Unity Editor

> Attackers can execute arbitrary code and steal data by exploiting argument injection in Unity Runtime, requiring developers to rebuild affected applications.

- **Severity:** High 7.4 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Oct 2025
- **Updated:** 3 Oct 2025
- **Also known as:** GHSA-427p-ppg4-cg5q

## What is CVE-2025-59489?

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.

### Official 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.

Weakness: CWE-426 (Untrusted Search Path), CWE-88 (Improper Neutralization of Argument Delimiters in a Command)

## Which versions are affected by CVE-2025-59489?

It affects 1 product.


Products: Unity Editor.

## How do I fix CVE-2025-59489?

No fix has been published for CVE-2025-59489 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-59489 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-59489 exists.

Public exploit code:

- Proof Of Concept For CVE-2025-59489. Affects unity games running on Android.  (github_poc): https://github.com/GithubKillsMyOpsec/CVE-2025-59489-POC
- CVE-2025-59489 Unity Vulnerability Checker (github_poc): https://github.com/taptap/cve-2025-59489

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-59489 and fix it if it is affected.

What 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-59489 exists.

Affected product: Unity3D Unity Editor. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-59489/ (Markdown: https://insights.sbomify.com/CVE-2025-59489/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-59489
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-59489
- OSV: https://osv.dev/vulnerability/CVE-2025-59489

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-59489/
Summaries are generated and may contain mistakes; the official description above is the record.