CVE Watchtower

CVE-2025-59489Unity Editor Argument Injection

NVDCVSS scored by cve@mitre.org

Vulnerability Summary

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.
Severity Level
HIGH(7.4)
Published Date
Oct 3, 2025
Last Modified
Oct 8, 2026
Exploitation Status
Public exploit available
EPSS Score (30-Day)
0.64%Probability
Root Weakness (CWE)
The product constructs a string for a command to be executed by a separate component, but it does not properly delimit the intended arguments, options, or switches within that string.
The product searches for critical resources using an externally-supplied search path that can point to resources outside its direct control.
CVSS v3.1 Base Metrics — Score 7.4 (HIGH)
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Attack VectorLocal
Attack ComplexityHigh
Privileges RequiredNone
User InteractionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh

Affected & Patched Versions

Affected Versions
  • Unity Editor >= 2017.4 and <= 2018.4
  • Unity Editor >= 2019.1 and < 2019.1.15f1
  • Unity Editor >= 2019.2 and < 2019.2.23f1
  • Unity Editor >= 2019.3 and <= 2019.3.17f1
  • Unity Editor >= 2019.4 and < 2019.4.41f1
  • Unity Editor >= 2020.1 and < 2020.1.18f1
  • Unity Editor >= 2020.2 and < 2020.2.8f1
  • Unity Editor >= 2020.3 and < 2020.3.49f1
  • Unity Editor >= 2021.1 and < 2021.1.29f1
  • Unity Editor >= 2021.2 and < 2021.2.20f1
  • Unity Editor >= 2021.3 and < 2021.3.45f2
  • Unity Editor >= 2022.1 and < 2022.1.25f1
  • Unity Editor >= 2022.2 and < 2022.2.23f1
  • Unity Editor >= 2022.3 and < 2022.3.62f2
  • Unity Editor >= 2023.1 and < 2023.1.22f1
  • Unity Editor >= 2023.2 and < 2023.2.22f1
  • Unity Editor >= 6000.0 and < 6000.0.58f2
  • Unity Editor >= 6000.1 and < 6000.1.17f1
  • Unity Editor >= 6000.2 and < 6000.2.6f2
  • Unity Editor >= 6000.3 and < 6000.3.0b4
  • Unity Editor
Patched Versions
  • Unity Editor 2019.1.15f1
  • Unity Editor 2019.2.23f1
  • Unity Editor 2019.4.41f1
  • Unity Editor 2020.1.18f1
  • Unity Editor 2020.2.8f1
  • Unity Editor 2020.3.49f1
  • Unity Editor 2021.1.29f1
  • Unity Editor 2021.2.20f1
  • Unity Editor 2021.3.45f2
  • Unity Editor 2022.1.25f1
  • Unity Editor 2022.2.23f1
  • Unity Editor 2022.3.62f2
  • Unity Editor 2023.1.22f1
  • Unity Editor 2023.2.22f1
  • Unity Editor 6000.0.58f2
  • Unity Editor 6000.1.17f1
  • Unity Editor 6000.2.6f2
  • Unity Editor 6000.3.0b4

What to do

Prioritize this fix. Exploit code is public, so attacks can follow quickly.

  1. Check whether you run Unity Editor and which version.
  2. Update to a patched version listed above, then confirm the new version.
  3. Review logs and exposed services for signs of earlier compromise.

Timeline

  • Oct 3, 2025Published
  • Oct 8, 2026Record last modified

Score, severity and exploitation changes are tracked from the day Watchtower started logging them.

Get notified about new Unity Editor CVEsYou are reading CVE-2025-59489. Get an email when KEV listings, exploits or new CVEs match your stack.
Set up CVE alerts

Data last checked: Nov 19, 2026 16:14 UTC