High Injection exploit reference

CVE-2025-59489 — Argument Injection in Unity Editor

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.

Published Oct 3, 2025 · Updated Oct 13, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: mitre

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

EPSS 0.6% (30-day exploitation probability)+7
Technical severity (high)+6
CISA SSVC: exploitation "poc"+5

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

0.64%

ahead of 50% of scored CVEs · Oct 14, 2026

Affects

Unity

Editor and 1 more

CVSS base

7.4

High · 4 source(s)

Prioritization reference: 8.4 provisional

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation

Proof of concept

none · proof-of-concept · active

Automatable

can an attacker script the kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Unity Editor, Unity3D Unity Editor).
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
Search available logs for exploit probes matching the vulnerability class (injection), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Unity	Editor	≥ 2019.1 and < 2019.1.15f1version 2017.3.0b9+version 2017.2.0p4+version 2017.1.2p4+≥ 6000.3 and < 6000.3.0b4≥ 6000.2 and < 6000.2.6f2≥ 6000.1 and < 6000.1.17f1≥ 6000.0 and < 6000.0.58f2 and 15 more ≥ 2023.2 and < 2023.2.22f1≥ 2023.1 and < 2023.1.22f1≥ 2022.3 and < 2022.3.62f2≥ 2022.2 and < 2022.2.23f1≥ 2021.3 and < 2021.3.45f2≥ 2022.1 and < 2022.1.25f1≥ 2017.4 and ≤ 2018.4≥ 2019.2 and < 2019.2.23f1≥ 2019.3 and ≤ 2019.3.17f1≥ 2019.4 and < 2019.4.41f1≥ 2020.1 and < 2020.1.18f1≥ 2020.2 and < 2020.2.8f1≥ 2020.3 and < 2020.3.49f1≥ 2021.1 and < 2021.1.29f1≥ 2021.2 and < 2021.2.20f1	Vulnerable	NIST National Vulnerability Database
Unity3D	Unity Editor	≥ 2017.1.2p4 and < 2019.1.15f1≥ 2019.2 and < 2019.2.23f1≥ 2019.3 and < 2019.3.17f1≥ 2019.4 LTS and < 2019.4.41f1≥ 2020.1 and < 2020.1.18f1≥ 2020.2 and < 2020.2.8f1≥ 2020.3 and < 2020.3.49f1≥ 2021.1 and < 2021.1.29f1 and 13 more ≥ 2021.2 and < 2021.2.20f1≥ 2021.3 LTS and < 2021.3.45f2≥ 2022.1 and < 2022.1.25f1≥ 2022.2 and < 2022.2.23f1≥ 2022.3 LTS and < 2022.3.62f2≥ 2023.1 and < 2023.1.22f1≥ 2023.2 and < 2023.2.22f1≥ 6000.1 and < 6000.1.17f1≥ 2021.3 xLTS and < 2021.3.56f2≥ 2022.3 xLTS and < 2022.3.67f2≥ 6000.0 LTS and < 6000.0.58f2≥ 6000.2 and < 6000.2.6f2≥ 6000.3 and < 6000.3.0b4	Vulnerable	CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Local

Attack complexity

High

Privileges required

None

User interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Scored by
8.4	CVSS 3.1	High	2.5	5.9	134c704f-9b21-4f2e-91b3-4a467353bcc0 via NIST National Vulnerability Database
8.4	CVSS 3.1	High	—	—	CISA-ADP via CVE Program (cve.org) e CISA ADP
7.4	CVSS 3.1	High	1.4	5.9	cve@mitre.org via NIST National Vulnerability Database
7.4	CVSS 3.1	High	—	—	mitre via CVE Program (cve.org) e CISA ADP

CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H (score shown at the top: cve@mitre.org)

Scoring entities (NIST, CNA, ADP) score independently; each score is shown with its origin. For prioritization we use 8.4 (CISA ADP via NIST National Vulnerability Database) as a conservative provisional reference — not a definitive official score.

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-88 · Argument Injection

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.64%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
Look for parameters with command/query metacharacters and unexpected child processes of the service.

endpoint telemetry (EDR)application logs

Timeline

What happened to this CVE, newest first.

2026
Affected products added · unity3d/unity editor
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
SSVC assessment updated
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
Record published
Oct 13, 2026
CVSS changed · 7.4
Oct 13, 2026 · NIST National Vulnerability Database
Source status changed · → Analyzed
Oct 13, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 13, 2026 · NIST National Vulnerability Database
2025
CVE published
Oct 3, 2025 · mitre

Source activity

Repeated readings are counted rather than listed.

1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

3 on the record

unity.com/security/sept-2025-01
Vendor Advisory, NIST National Vulnerability Database
flatt.tech/research/posts/arbitrary-code-execution-in-unity-runtime/
Exploit, Third Party Advisory, NIST National Vulnerability Database
unity.com/security
Product, NIST National Vulnerability Database

Elsewhere on this site

Unity
every CVE for this vendor

Injection
same class

CWE-88
other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No fixed version, patch or mitigation documented.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2025-59489 is "Argument Injection in Unity Editor", rated High. It affects Editor (Unity); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.4 describes technical severity. EPSS 0.64% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.