Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Unity3D | Unity Editor | unaffected |
|
Configuration 1 [-]
| AND |
|
No data.
| Vendor | Product | Versions |
|---|---|---|
| Apple | Macos | — |
| Linux | Linux | — |
| Microsoft | Windows | — |
| Unity3d | Unity Editor | — |
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2025-32292 | 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. |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.857% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Google
Google android Linux linux Kernel Unity Unity editor |
|
| CPEs | cpe:2.3:a:unity:editor:*:*:*:*:-:*:*:* cpe:2.3:a:unity:editor:*:*:*:*:lts:*:*:* cpe:2.3:a:unity:editor:2017.1.2p4\+:*:*:*:-:*:*:* cpe:2.3:a:unity:editor:2017.2.0p4\+:*:*:*:-:*:*:* cpe:2.3:a:unity:editor:2017.3.0b9\+:*:*:*:-:*:*:* cpe:2.3:o:apple:macos:-:*:*:*:*:*:*:* cpe:2.3:o:google:android:-:*:*:*:*:*:*:* cpe:2.3:o:linux:linux_kernel:-:*:*:*:*:*:*:* cpe:2.3:o:microsoft:windows:-:*:*:*:*:*:*:* |
|
| Vendors & Products |
Google
Google android Linux linux Kernel Unity Unity editor |
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Apple
Apple macos Linux Linux linux Microsoft Microsoft windows Unity3d Unity3d unity Editor |
|
| Vendors & Products |
Apple
Apple macos Linux Linux linux Microsoft Microsoft windows Unity3d Unity3d unity Editor |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Unity Editor 2019.1 through 6000.3 could allow remote attackers to exploit file loading and Local File Inclusion (LFI) mechanisms via a crafted local application because of an Untrusted Search Path. This could permit unauthorized manipulation of runtime resources and third-party integrations. The issue could affect applications built using Unity and deployed across Android, Windows, macOS, and Linux platforms. | 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. |
| Weaknesses | CWE-88 | |
| Metrics |
cvssV3_1
|
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-426 | |
| Metrics |
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Unity Editor 2019.1 through 6000.3 could allow remote attackers to exploit file loading and Local File Inclusion (LFI) mechanisms via a crafted local application because of an Untrusted Search Path. This could permit unauthorized manipulation of runtime resources and third-party integrations. The issue could affect applications built using Unity and deployed across Android, Windows, macOS, and Linux platforms. | |
| References |
|