An input string validation issue was identified that could lead to Remote Code Execution (RCE), allowing an attacker to potentially execute code remotely in the user’s computer.

No. Only the Unity Editor is affected.

Windows only. Mac and Linux platforms are not affected by the identified vulnerability.

All versions of Windows.

All versions of the Unity Editor running on Windows.

We have released a patch for the latest Unity Editor versions of 5.6 and all officially supported versions up to 2019.2 Alpha. All future versions will contain the update as well.

Unity will be releasing a single patch to each of the most current, i.e., last update of the Unity Editor.

We are providing a mitigation tool that disables the identified vulnerable feature of the Unity Editor which can be downloaded from the Mitigation Tool Guide [7].

Please take into account that the mitigation is not a patch and has limitations. The mitigation will disable the Unity Editor feature identified as vulnerable, but since we can not control whether the affected functionality becomes re-enabled at some point after applying the mitigation, we strongly recommend updating to a fixed version of the Unity Editor to get the benefits of the full patch. You will also no longer be able to use the ‘Open in Unity’ functionality in the web browser version of the Asset Store after applying the mitigation.

The mitigation tool can be used on all affected versions of the Unity Editor.

Please take into account that the mitigation is not a patch and has limitations. The mitigation will disable the Unity Editor feature identified as vulnerable, but since we can not control whether the affected functionality becomes re-enabled at some point after applying the mitigation, we strongly recommend updating to a fixed version of the Unity Editor to get the benefits of the full patch. You will also no longer be able to use the ‘Open in Unity’ functionality in the web browser version of the Asset Store after applying the mitigation.

No, by running it once it deactivates the identified vulnerable component across all of them. Do keep in mind that by re-installing or updating (one) of the versions, it may activate the component again. To check, re-run the workaround tool until all versions are up to date.

The mitigation will disable the Unity Editor feature identified as vulnerable, but since we can not control whether the affected functionality becomes re-enabled at some point after applying the mitigation, we strongly recommend updating to a fixed version of the Unity Editor to get the benefits of the full patch. You will also no longer be able to use the ‘Open in Unity’ functionality in the web browser version of the Asset Store after applying the mitigation.

Our focus right now is on addressing the identified vulnerability in 5.6 and all officially supported versions up to 2019.2 Alpha. We do not have any details to share on patches for other versions at this time.

It depends on the specific version of the Unity Editor that you are using. Most customers will be able to update to the patched versions without needing to rebuild their bundles, but some customers may find that asset importers have been updated between the version they are currently using and the patch for that dot-release. For those customers, asset bundle rebuilding may be necessary.

You may need to rebuild your bundles if any assets are re-imported when you first open your project in the patched version of the Unity Editor.