| Package | Affected versions | Patched versions |
|---|---|---|
| Microsoft.Build.Tasks.Git | = 8.0.0≥ 10.0.102, < 10.0.111≥ 10.0.200, ≤ 10.0.204≥ 10.0.300, < 10.0.303 | 10.0.11110.0.303 |
| Microsoft.SourceLink.AzureRepos.Git | = 8.0.0≥ 10.0.102, < 10.0.111≥ 10.0.200, ≤ 10.0.204≥ 10.0.300, < 10.0.303 | 10.0.11110.0.303 |
| .net | ≥ 10.0.0, < 10.0.11≥ 8.0.0, < 8.0.30≥ 9.0.0, < 9.0.19 | 10.0.118.0.309.0.19 |
| visual studio 2022 | ≥ 17.14.0, < 17.14.38 | 17.14.38 |
| visual studio 2026 | ≥ 18.8.0, < 18.8.3 | 18.8.3 |
Microsoft is releasing this security advisory to provide information about a vulnerability in Microsoft.Build.Tasks.Git and Microsoft.SourceLink.AzureRepos.Git. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability.
Improper removal of sensitive information before storage or transfer in .NET allows an unauthorized attacker to disclose information over a network.
Announcement for this issue can be found at https://github.com/dotnet/announcements/issues/**TBD**
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N/E:U/RL:O/RC:CThe vulnerability affects any Microsoft .NET project if it uses any of affected package versions listed below
| Package name | Affected version | Patched version |
|---|---|---|
| Microsoft.Build.Tasks.Git | = 8.0.0 | No patched NuGet version; update to a fixed .NET 8 SDK |
| Microsoft.Build.Tasks.Git | >= 10.0.102, <= 10.0.110 | 10.0.111 |
| Microsoft.Build.Tasks.Git | >= 10.0.200, <= 10.0.204 | No patched NuGet version; the 10.0.2xx SDK feature band is no longer serviced |
| Microsoft.Build.Tasks.Git | >= 10.0.300, <= 10.0.301 | 10.0.303 |
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free| Microsoft.SourceLink.AzureRepos.Git | = 8.0.0 | No patched NuGet version; update to a fixed .NET 8 SDK |
| Microsoft.SourceLink.AzureRepos.Git | >= 10.0.102, <= 10.0.110 | 10.0.111 |
| Microsoft.SourceLink.AzureRepos.Git | >= 10.0.200, <= 10.0.204 | No patched NuGet version; the 10.0.2xx SDK feature band is no longer serviced |
| Microsoft.SourceLink.AzureRepos.Git | >= 10.0.300, <= 10.0.301 | 10.0.303 |
The affected packages used by .NET 8 and .NET 9 SDKs are built with SDK-specific prerelease versions that aren't published as stable NuGet packages. Update to SDK 8.0.130 or 8.0.424, SDK 9.0.120 or 9.0.317, or SDK 10.0.111 or 10.0.303 to receive the fix.
If using a package listed in affected packages, you're exposed to the vulnerability.
dotnet --info command.Once you have installed the updated runtime or SDK, restart your apps for the update to take effect.
Additionally, if you've deployed self-contained applications targeting any of the impacted versions, these applications are also vulnerable and must be recompiled and redeployed.
If you have found a potential security issue in a supported version of .NET, please report it to the Microsoft Security Response Center (MSRC) via the MSRC Researcher Portal. Further information can be found in the MSRC Report an Issue FAQ.
Security reports made through MSRC may qualify for the Microsoft .NET Bounty. Details of the Microsoft .NET Bounty Program including terms and conditions are at https://aka.ms/corebounty.
You can ask questions about this issue on GitHub in the .NET GitHub organization. The main repos are located at https://github.com/dotnet/runtime. The Announcements repo (https://github.com/dotnet/Announcements) 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.
Ivan Demchuk
V1.0 (08/11/2026): Advisory published.