# CVE-2026-62900: Microsoft .NET information disclosure in Git and SourceLink

Source: https://junglewise.ai/threats/cve-2026-62900-microsoft-net-information-disclosure-in-git-and-sourcelink  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-08-11. Updated: 2026-09-25  
License: CC BY 4.0 with a link back

CVE-2026-62900 · Severity: medium · CVSS 5.9 · Published 2026-08-11

Microsoft.Build.Tasks.Git and Microsoft.SourceLink.AzureRepos.Git fail to properly remove sensitive information before storing or transferring data. An attacker with network access could exploit this flaw to disclose confidential information such as credentials, tokens, or other secrets embedded in build metadata or source link information. This affects developers using vulnerable versions of the .NET SDK and could compromise authentication credentials or internal system details.

Technologies: [Apple macOS](https://junglewise.ai/threats/technologies/macos), [Linux Kernel](https://junglewise.ai/threats/technologies/kernel), [Microsoft .Net](https://junglewise.ai/threats/technologies/microsoft-net), [Microsoft Visual Studio 2022](https://junglewise.ai/threats/technologies/visual-studio-2022), [Microsoft Visual Studio 2026](https://junglewise.ai/threats/technologies/visual-studio), [Microsoft Windows](https://junglewise.ai/threats/technologies/windows). Vendors: [Apple](https://junglewise.ai/threats/vendors/apple), [Linux](https://junglewise.ai/threats/vendors/linux), [Microsoft](https://junglewise.ai/threats/vendors/microsoft), [NuGet](https://junglewise.ai/threats/vendors/nuget).

## Quick answers

**Is CVE-2026-62900 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-62900 being exploited in the wild.

**How severe is CVE-2026-62900?** Medium severity, with a CVSS score of 5.9, published 11 August 2026.

**Which products and versions are affected?** Microsoft .NET SDK 8.x, 9.x, 10.x; Microsoft.Build.Tasks.Git (NuGet) ECOSYSTEM:introduced=10.0.102,fixed=10.0.111; Microsoft.SourceLink.AzureRepos.Git (NuGet) ECOSYSTEM:introduced=10.0.102,fixed=10.0.111.

**Is there a fix for CVE-2026-62900?** Yes. Microsoft.Build.Tasks.Git (NuGet): upgrade to 10.0.111 or later; Microsoft.SourceLink.AzureRepos.Git (NuGet): upgrade to 10.0.111 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-62900 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-62900?** Check whether you run Apple macOS, Linux Kernel, Microsoft .Net or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- Microsoft.Build.Tasks.Git (NuGet): upgrade to 10.0.111 or later

  ```sh
  dotnet add package Microsoft.Build.Tasks.Git --version 10.0.111
  ```

- Microsoft.SourceLink.AzureRepos.Git (NuGet): upgrade to 10.0.111 or later

  ```sh
  dotnet add package Microsoft.SourceLink.AzureRepos.Git --version 10.0.111
  ```


## Technical details

The vulnerability exists in Microsoft.Build.Tasks.Git and Microsoft.SourceLink.AzureRepos.Git NuGet packages, which are used during .NET project builds to embed Git and Azure Repos metadata. These components fail to sanitize sensitive information (such as authentication credentials, personal access tokens, or connection strings) before storing or transferring build metadata. The root cause is classified as CWE-212: Improper Removal of Sensitive Information Before Storage or Transfer. An attacker with network visibility can intercept or access this unredacted sensitive data during the build process or when source link information is referenced. Exploitation requires high attack complexity (likely involving specific build conditions or network positioning), no authentication, and no user interaction. Patches are available for 10.0.111 and 10.0.303 NuGet versions; however, versions 8.0.0 and the 10.0.2xx branch require SDK-level updates (.NET 8.0.130/424, 9.0.120/317, or 10.0.111/303). Self-contained applications must be recompiled and redeployed to receive the fix.

## Affected products

- Microsoft Microsoft.Build.Tasks.Git 8.0.0, 10.0.102–10.0.110, 10.0.200–10.0.204, 10.0.300–10.0.301
- Microsoft Microsoft.SourceLink.AzureRepos.Git 8.0.0, 10.0.102–10.0.110, 10.0.200–10.0.204, 10.0.300–10.0.301
- Microsoft .NET SDK 8.x, 9.x, 10.x

## Identifiers

- CVE-2026-62900
- GHSA-23fw-v26w-5fgq

## Timeline

- 2026-08-11: disclosed: Security advisory published by Microsoft
- 2026-09-08: advisory: Advisory updated and published to GitHub Advisory Database

## References

- [https://github.com/dotnet/sourcelink/security/advisories/GHSA-23fw-v26w-5fgq](https://github.com/dotnet/sourcelink/security/advisories/GHSA-23fw-v26w-5fgq)
- [https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-62900](https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-62900)
- [https://api.github.com/repos/dotnet/sourcelink/security-advisories/GHSA-23fw-v26w-5fgq](https://api.github.com/repos/dotnet/sourcelink/security-advisories/GHSA-23fw-v26w-5fgq)

## Related threats

- [Linux IOMMU page table logic error in arm_lpae_split_blk_unmap](https://junglewise.ai/threats/cve-2026-56934-in-arm-lpae-split-blk-unmap-of-drivers-iommu-io-pgtable-arm)
- [Linux kernel null pointer dereference in TCP established lookup](https://junglewise.ai/threats/cve-2026-99288-in-the-linux-kernel-the-following-vulnerability-has-been-resolved)
- [Linux kernel xen-netback race condition in XenBus disconnect](https://junglewise.ai/threats/cve-2026-99286-in-the-linux-kernel-the-following-vulnerability-has-been-resolved)
- [Windows BitLocker heap buffer overflow with physical attack](https://junglewise.ai/threats/cve-2026-97015-heap-based-buffer-overflow-in-windows-bitlocker-allows-an)
- [Microsoft Windows Shell type confusion privilege elevation](https://junglewise.ai/threats/cve-2026-97013-access-of-resource-using-incompatible-type-type-confusion-in)