Microsoft is releasing this security advisory to provide information a vulnerability in .NET 8.0, and .NET 9.0. This advisory also provides guidance on what developers can do to update their environments to remove this vulnerability.
An attacker could exploit this vulnerability to writing a specially crafted file in the security context of the local system. This only affects .NET on Linux operating systems.
Announcement for this issue can be found at dotnet/sdk#45959
Microsoft has not identified any mitigating factors for this vulnerability.
The vulnerability does not affect Microsoft .NET packages.
How do I know if I am affected?
If you have an SDK with a version listed, you're exposed to the vulnerability.
How do I fix the issue?
To fix the issue please install the latest version of .NET 8.0 SDK or .NET 9.0 SDK, as appropriate.
You can list the versions you have installed by running the dotnet --info command. You will see output like the following;
Once you have installed the updated SDK, restart your apps for the update to take effect.
Reporting Security Issues
If you have found a potential security issue in .NET 8.0 or .NET 9.0, please email details to [email protected] . Reports may qualify for the Microsoft .NET Core & .NET 5 Bounty. Details of the Microsoft .NET Bounty Program including terms and conditions are at .
You can ask questions this issue on GitHub in the .NET GitHub organization. The main repos are located at . The Announcements repo ( ) will contain this bulletin as an issue and will include a link to a discussion issue. You can ask questions in the linked discussion issue.
The information provided in this advisory is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.
V1.1 (May 30, 2025): Added specific SDK version information. V1.0 (January 14, 2024): Advisory published.
dotnet locked and limited conversation to collaborators on Jan 14, 2025
rbhanda added Security on Jan 14, 2025
The full story
This article is one source in a clustered incident — the cluster page carries the summary, timeline and every other outlet covering it.
