dbcve.org
EditorApplication · Unity

CVE-2025-59489

HIGH · 7.4 CVSS v3.1 Published 2025-10-03
Fix available
A fix is available. Upgrade to 2019.1.15f1 / 2019.2.23f1 or later.
See remediation →
79/100
Remediation priority · High
Public exploit No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
EditorApplication
Affected:>= 2017.4, <= 2018.4>= 2019.1, < 2019.1.15f1>= 2019.2, < 2019.2.23f1>= 2019.3, <= 2019.3.17f1>= 2019.4, < 2019.4.41f1>= 2020.1, < 2020.1.18f1>= 2020.2, < 2020.2.8f1>= 2020.3, < 2020.3.49f1>= 2021.1, < 2021.1.29f1>= 2021.2, < 2021.2.20f1>= 2021.3, < 2021.3.45f2>= 2022.1, < 2022.1.25f1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2019.1.15f1 / 2019.2.23f1 / 2019.4.41f1 or later
Fixed in 2019.1.15f12019.2.23f12019.4.41f1
Recommended fix Moderate confidence

Unity 2019.4f1 (LTS) or later (specifically: 2019.1.15f1, 2019.2.23f1, >2019.3.17f1)

  1. 1. Identify all Unity Editor versions currently in use for building your affected applications.
  2. 2. For each affected application, determine which Unity Editor version was used to build it originally.
  3. 3. If originally built with Unity 2019.1.x, rebuild the application using Unity 2019.1.15f1 or later.
  4. 4. If originally built with Unity 2019.2.x, rebuild the application using Unity 2019.2.23f1 or later.
  5. 5. If originally built with Unity 2019.3.x, rebuild the application using a version newer than 2019.3.17f1 (such as 2019.4f1 or later LTS).
  6. 6. If originally built with Unity 2017.4.x or 2018.4.x, upgrade to Unity 2019.4f1 (LTS) or later and rebuild the application.
  7. 7. After rebuilding, redeploy the updated applications to all end-user devices to address the runtime vulnerability.
  8. 8. Ensure your development pipeline now uses a non-vulnerable Unity Editor version for future builds.
Caveat Upgrading Unity Editor versions between major releases may require code adjustments; test thoroughly before redeploying

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-59489 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-59489 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data