Unity Runtime before 2025-10-02 on Android, Windows, macOS, and Linux allows argument injection that can result in loading of library code f

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.

Timeline

1. Oct 3, 2025, 12:00 AM UTCCVE published
2. Oct 3, 2025, 1:54 PM UTCCISA SSVC assessment

   Exploitation: poc · Automatable: no · Technical impact: total

3. Oct 3, 2025, 5:22 PM UTCRecord last updated

Affected versions

• Unity3D Unity Editor

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

References 5