
Summary
Applications that were built using affected versions of the Unity Editor are susceptible to an unsafe file loading and local file inclusion attack depending on the operating system, which could enable local code execution or information disclosure at the privilege level of the vulnerable application. There is no evidence of any exploitation of the vulnerability nor has there been any impact on users or customers. Unity has provided fixes that address the vulnerability and they are already available to all developers.
Vulnerability Details
CVE ID: CVE-2025-59489
Date Discovered: June 4, 2025
Discovered By: RyotaK of GMO Flatt Security Inc.
Date Patch Available: October 2, 2025
Affected Operating System: See Affected Operating Systems Table
Affected Versions: See Unity Editor Versions Table
Patched Versions: See Unity Editor Versions Table
Vulnerability Type: CWE-426: Untrusted Search Path
Severity: High
CVSS Score: 8.4
CVSS Vector String: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Exploitation Potential
Could allow local code execution and access to confidential information on end user devices running unity-built applications. Code execution would be confined to the privilege level of the vulnerable application, and information disclosure would be confined to the information available to the vulnerable application.There is no evidence of any exploitation of the vulnerability nor has there been any impact on users or customers.
Unity Editor Versions
Applications built with the indicated versions of the Unity Editor prior to the Patched Versions are considered vulnerable.
Current in Support Versions
Affected Versions
6000.3
6000.3.0b4
6000.2
6000.2.6f2
6000.0 LTS
6000.0.58f2
2022.3 xLTS
2022.3.67f2
2021.3 xLTS
2021.3.56f2
6000.3.0b4
6000.2
6000.2.6f2
6000.0 LTS
6000.0.58f2
2022.3 xLTS
2022.3.67f2
2021.3 xLTS
2021.3.56f2
Out of Support Versions
Affected Versions
6000.1
6000.1.17f1
2023.2
2023.2.22f1
2023.1
2023.1.22f1
2022.3 LTS
2022.3.62f2
2022.2
2022.2.23f1
2022.1
2022.1.25f1
2021.3 LTS
2021.3.45f2
2021.2
2021.2.20f1
2021.1
2021.1.29f1
2020.3
2020.3.49f1
2020.2
2020.2.8f1
2020.1
2020.1.18f1
2019.4 LTS
2019.4.41f1
2019.3
2019.3.17f1
2019.2
2019.2.23f1
2019.1
2019.1.15f1
2018.4
2018.3
2018.2
2018.1
2017.4
2017.3
2017.3.0b9+
2017.2
2017.2.0p4+
2017.1
2017.1.2p4+
6000.1.17f1
2023.2
2023.2.22f1
2023.1
2023.1.22f1
2022.3 LTS
2022.3.62f2
2022.2
2022.2.23f1
2022.1
2022.1.25f1
2021.3 LTS
2021.3.45f2
2021.2
2021.2.20f1
2021.1
2021.1.29f1
2020.3
2020.3.49f1
2020.2
2020.2.8f1
2020.1
2020.1.18f1
2019.4 LTS
2019.4.41f1
2019.3
2019.3.17f1
2019.2
2019.2.23f1
2019.1
2019.1.15f1
2018.4
2018.3
2018.2
2018.1
2017.4
2017.3
2017.3.0b9+
2017.2
2017.2.0p4+
2017.1
2017.1.2p4+
Affected Platforms Table
Applications built with affected versions of the Unity Editor and released on these platforms could be impacted by the vulnerability.
Note: If a platform is not listed, there have been no findings to suggest that the vulnerability is exploitable.
Impact
Android
Code Execution / Elevation of Privilege
Windows
Elevation of Privilege
Linux (Desktop)
Elevation of Privilege
Linux (Embedded)
Elevation of Privilege
MacOS
Elevation of Privilege
On Microsoft Windows systems, the presence of a registered custom URI handler for a vulnerable application or handler name could increase the risk of exploitation. If a custom URI scheme is present and can be invoked on the target system, an attacker who can cause that URI to be opened could trigger the vulnerable library-loading behavior without needing direct command-line access. Potential exploitation remains constrained to the privileges of the targeted application and to the data and services accessible to that process. Entities that routinely create registered URI handlers for Unity applications are encouraged to contact Unity directly at security@unity3d.com.
Discovery
This vulnerability was responsibly reported by an external security researcher.
Remediation Steps
Rebuild Application
Update the Unity Editor to the newest version then rebuild and redeploy the application.
Binary Patch
Using the Unity Binary Patch tool for the target platform, the Unity runtime library can be replaced with a patched version of the library.
Unity Fixed Versions
Unity fixed versions: Direct links to the first fixed versions of the Unity Editor (which includes the Unity Runtime as well)
Patched Version
6000.3.0b4
6000.2.6f2
6000.1.17f1
6000.0.58f2
2023.2.22f1
2023.1.22f1
2022.3.67f2
2022.3.62f2
2022.2.23f1
2022.1.25f1
2021.3.56f2
2021.3.45f2
2021.2.20f1
2021.1.29f1
2020.3.49f1
2020.2.8f1
2020.1.18f1
2019.4.41f1
2019.3.17f1
2019.2.23f1
2019.1.15f1
6000.2.6f2
6000.1.17f1
6000.0.58f2
2023.2.22f1
2023.1.22f1
2022.3.67f2
2022.3.62f2
2022.2.23f1
2022.1.25f1
2021.3.56f2
2021.3.45f2
2021.2.20f1
2021.1.29f1
2020.3.49f1
2020.2.8f1
2020.1.18f1
2019.4.41f1
2019.3.17f1
2019.2.23f1
2019.1.15f1
FAQ
My application or game is released on a platform or operating system not listed, what should I do?
If an application or game is released to a platform we have not listed, there have been no findings to suggest that the vulnerability is exploitable. For added security, however, we recommend that you rebuild your games and applications with updated Unity versions.
How was the vulnerability discovered?
The vulnerability was initially discovered by a third-party researcher.
What is the process for reporting future vulnerabilities to Unity?
We have a Responsible Disclosure policy as a part of our cooperation with internal and external security researchers and also have a Bug Bounty program. For more information on our Bug Bounty program, contact security@unity3d.com or visit our Bug Bounty program on Bugcrowd.
https://unity.com/security/sept-2025-01 (Archive)
