安装 Steam
登录
|
语言
繁體中文（繁体中文）
日本語（日语）
한국어（韩语）
ไทย（泰语）
български（保加利亚语）
Čeština（捷克语）
Dansk（丹麦语）
Deutsch（德语）
English（英语）
Español-España（西班牙语 - 西班牙）
Español - Latinoamérica（西班牙语 - 拉丁美洲）
Ελληνικά（希腊语）
Français（法语）
Italiano（意大利语）
Bahasa Indonesia（印度尼西亚语）
Magyar（匈牙利语）
Nederlands（荷兰语）
Norsk（挪威语）
Polski（波兰语）
Português（葡萄牙语 - 葡萄牙）
Português-Brasil（葡萄牙语 - 巴西）
Română（罗马尼亚语）
Русский（俄语）
Suomi（芬兰语）
Svenska（瑞典语）
Türkçe（土耳其语）
Tiếng Việt（越南语）
Українська（乌克兰语）
报告翻译问题
讨论规则及指引
0 
举报此帖
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.
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.