From what I've been able to read so far....

Unity devs have already updated their code to eliminate the vulnerability. Now the game devs have to either rebuild their games with the new code or swap out a DLL file. They will then have to publish that newly built game to Steam which will then build patches to the users to update their games. Big dev houses like Microsoft's have already been doing this.

In the meantime, if you run them with Steam, Steam will warn you if it's being launched with the susceptible command line arguments and give you the option to ignore the warning or stop the game.

So it's up to you if don't think enough is being done to protect you. Your unity games are only vulnerable if certain command line arguments are used. Otherwise, they are safe. And Steam is intervening where necessary to protect you.

Thx for the answer

Just tested two Unity games - Pillars of Eternity and Pillars of Eternity Deadfire. Both boot with zero issues, no warning screen due to not using command line arguments.

Oprindeligt skrevet af Nx Machina:

Just tested two Unity games - Pillars of Eternity and Pillars of Eternity Deadfire. Both boot with zero issues, no warning screen due to not using command line arguments.

It's on the last steam update :

Added mitigations for Unity CVE-2025-59489, blocking a game launch through the Steam Client when an exploit attempt is detected.