cve.bz

CVE-2025-59489 unity editor: Argument Injection

7.4 highExploit referenceEPSS 0.9%

High (7.4) in unity editor. EPSS 0.9% estimated probability of exploitation activity in the next 30 days.

On this page
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

CVSS 3.1

7.4 high
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
0.9% (up from 0.6% a week ago; 0.6% 30 days ago) estimated probability of exploitation activity in the next 30 days; 59th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: total, assessed 2025-10-03. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-88 Improper Neutralization of Argument Delimiters in a Command (Argument Injection)
CWE-426 Untrusted Search Path
OWASP Top 10
A05:2025 Injection, A08:2025 Software or Data Integrity Failures
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-59489 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-59489?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-59489?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-59489 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Unity3D Unity Editorfrom 6000.3 before 6000.3.0b4
Unity3D Unity Editorfrom 6000.2 before 6000.2.6f2
Unity3D Unity Editorfrom 6000.0 LTS before 6000.0.58f2
Unity3D Unity Editorfrom 2022.3 xLTS before 2022.3.67f2
Unity3D Unity Editorfrom 2021.3 xLTS before 2021.3.56f2
Unity3D Unity Editorfrom 6000.1 before 6000.1.17f1
Unity3D Unity Editorfrom 2023.2 before 2023.2.22f1
Unity3D Unity Editorfrom 2023.1 before 2023.1.22f1
Unity3D Unity Editorfrom 2022.3 LTS before 2022.3.62f2
Unity3D Unity Editorfrom 2022.2 before 2022.2.23f1
Unity3D Unity Editorfrom 2022.1 before 2022.1.25f1
Unity3D Unity Editorfrom 2021.3 LTS before 2021.3.45f2
Unity3D Unity Editorfrom 2021.2 before 2021.2.20f1
Unity3D Unity Editorfrom 2021.1 before 2021.1.29f1
Unity3D Unity Editorfrom 2020.3 before 2020.3.49f1
Unity3D Unity Editorfrom 2020.2 before 2020.2.8f1
Unity3D Unity Editorfrom 2020.1 before 2020.1.18f1
Unity3D Unity Editorfrom 2019.4 LTS before 2019.4.41f1
Unity3D Unity Editorfrom 2019.3 before 2019.3.17f1
Unity3D Unity Editorfrom 2019.2 before 2019.2.23f1
Unity3D Unity Editorfrom 2017.1.2p4 before 2019.1.15f1

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

Attack patterns (CAPEC)

  • CAPEC-38 Leveraging/Manipulating Configuration File Search Paths Likelihood: High · Severity: Very High
  • CAPEC-41 Using Meta-characters in E-mail Headers to Inject Malicious Payloads Likelihood: High · Severity: High
  • CAPEC-88 OS Command Injection Likelihood: High · Severity: High
  • CAPEC-137 Parameter Injection Likelihood: Medium · Severity: Medium
  • CAPEC-174 Flash Parameter Injection Likelihood: High · Severity: Medium
  • CAPEC-460 HTTP Parameter Pollution (HPP) Severity: Medium

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON