CVE-2026-62900

mediumPriorität · verfolgen · 0EPSS 0.007 · 55. PerzentilDEEUNLRUUS
grimoire priorityP3 · Track
Exploitable?
—
no known exploitation
Likely / severe?
0.75% (55th) EPSS
CVSS 5.9 · medium
Is it mine?
177 products
Prüfe deine Angriffsfläche
Who says so?
7 sources
cnnvd · enisa_euvd · fstec_bdu · osv

EPSS · bewertet 2026-10-27

Improper removal of sensitive information before storage or transfer in .NET allows an unauthorized attacker to disclose information over a network.

01

Behebungen

Hersteller-Fix, Mitigation oder Workaround, wie von den Quellen veröffentlicht.

Ein Hersteller-Fix ist verfügbar.

02

cvss

Technischer Schweregrad, 0–10. Eine Zeile je Quelle.

5.9
010

Basiswert 0–10 · höher = schwerwiegender · Vektor überfahren zum Auflösen

v3.15.9mediumAV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:Nsecondary · FSTEC (BDU) RU
v3.15.9mediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N/E:U/RL:O/RC:Csecondary · ENISA EU
v3.15.9mediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:Nsecondary · secure@microsoft.com USAusnutzbarkeit 2.2 · Auswirkung 3.6
v3.15.9mediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:Nsecondary · OSV
v3.15.4mediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N/E:Usecondary · CVSS-BT (t0sche)
v3.15.9mediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:Nsecondary · NCSC-NL NL
v3.15.9mediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N/E:U/RL:O/RC:Csecondary · Microsoft Security Response Center US
03

SSVC

Eine Handlungsentscheidung — aus Ausnutzung und Auswirkung.

Trackcoordinatorcisa_ssvcUS
04

schwächen

Die CWE-Schwächeklassen, zu denen dies gehört.

05

betroffene Produkte (177)

Betroffene Produkte und Versionsbereiche.

20 von 177 angezeigt
06

Advisories (6)

Hersteller- und Ökosystem-Meldungen dazu.

  • NCSC-2026-0285Kwetsbaarheden verholpen in Microsoft Developer ToolsNL2026-08-11csaf · ncsc_nlNL

    Microsoft heeft kwetsbaarheden verholpen in diverse Developer Tools.

  • WID-SEC-W-2026-2761Microsoft Developer Tools: Mehrere SchwachstellenDeutsch2026-08-11csaf · cert_bundDE

    Ein Angreifer kann mehrere Schwachstellen in Microsoft Visual Studio Code, Microsoft Windows Server 2012, Microsoft Windows Server 2012 R2, Microsoft Windows Server 2016, Microsoft .NET Framework, Microsoft Windows Server 2019, Microsoft Windows Server 2022, Microsoft Windows Server 2025, Microsoft PowerShell, Microsoft Windows, Microsoft .NET, Microsoft Visual Studio 2022 und Microsoft Visual Studio 2026 ausnutzen, um beliebigen Programmcode auszuführen, um seine Privilegien zu erhöhen, um einen Denial of Service Angriff durchzuführen, um Informationen offenzulegen, und um Sicherheitsvorkehrungen zu umgehen.

  • msrc_CVE-2026-62900.NET Information Disclosure Vulnerability2026-08-11csaf · msrc_csafUS

    To determine the support lifecycle for your software, see the Microsoft Support Lifecycle: https://support.microsoft.com/lifecycle

  • GHSA-23fw-v26w-5fgqMicrosoft Security Advisory CVE-2026-62900 – .NET Information Disclosure Vulnerability2026-09-08ghsa · osvUS

    ## Executive summary 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 Announcement for this issue can be found at https://github.com/dotnet/announcements/issues/**TBD** ## CVSS Details - **Version:** 3.1 - **Severity:** Medium - **Score:** 5.9 - **Vector:** `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N/E:U/RL:O/RC:C` - **Weakness:** CWE-212: Improper Removal of Sensitive Information Before Storage or Transfer ## Affected Platforms - **Platforms:** Windows, Linux, macOS - **Architectures:** All ## <a name="affected-packages"></a>Affected Packages The vulnerability affects any Microsoft .NET project if it uses any of affected package versions listed below ### <a name="published-nuget-packages"></a>Published NuGet packages Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- [Microsoft.Build.Tasks.Git](https://www.nuget.org/packages/Microsoft.Build.Tasks.Git) | = 8.0.0 | No patched NuGet version; update to a fixed .NET 8 SDK [Microsoft.Build.Tasks.Git](https://www.nuget.org/packages/Microsoft.Build.Tasks.Git) | >= 10.0.102, <= 10.0.110 | 10.0.111 [Microsoft.Build.Tasks.Git](https://www.nuget.org/packages/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](https://www.nuget.org/packages/Microsoft.Build.Tasks.Git) | >= 10.0.300, <= 10.0.301 | 10.0.303 [Microsoft.SourceLink.AzureRepos.Git](https://www.nuget.org/packages/Microsoft.SourceLink.AzureRepos.Git) | = 8.0.0 | No patched NuGet version; update to a fixed .NET 8 SDK [Microsoft.SourceLink.AzureRepos.Git](https://www.nuget.org/packages/Microsoft.SourceLink.AzureRepos.Git) | >= 10.0.102, <= 10.0.110 | 10.0.111 [Microsoft.SourceLink.AzureRepos.Git](https://www.nuget.org/packages/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](https://www.nuget.org/packages/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. ## Advisory FAQ ### <a name="how-affected"></a>How do I know if I am affected? If using a package listed in [affected packages](#affected-packages), you're exposed to the vulnerability. ### <a name="how-fix"></a>How do I fix the issue? 1. To fix the issue please install the latest version of .NET. If you have installed one or more .NET SDKs through Visual Studio, Visual Studio will prompt you to update Visual Studio, which will also update your .NET SDKs. 2. If your application references the vulnerable package, update the package reference to the patched version. You can list the versions you have installed by running the `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](https://docs.microsoft.com/dotnet/core/deploying/#self-contained-deployments-scd) targeting any of the impacted versions, these applications are also vulnerable and must be recompiled and redeployed. ## Other Information ### Reporting Security Issues 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](https://msrc.microsoft.com/report/vulnerability/new). Further information can be found in the MSRC [Report an Issue FAQ](https://www.microsoft.com/msrc/faqs-report-an-issue). 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. ### Support 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. ### Disclaimer 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. ### External Links [CVE-2026-62900](https://www.cve.org/CVERecord?id=CVE-2026-62900) ### Acknowledgements Ivan Demchuk ### Revisions V1.0 (08/11/2026): Advisory published.

  • BIT-dotnet-2026-62900.NET Information Disclosure Vulnerability2026-08-17vendor · osvUS

    Improper removal of sensitive information before storage or transfer in .NET allows an unauthorized attacker to disclose information over a network.

  • BIT-dotnet-sdk-2026-62900.NET Information Disclosure Vulnerability2026-08-17vendor · osvUS

    Improper removal of sensitive information before storage or transfer in .NET allows an unauthorized attacker to disclose information over a network.

07

auch bekannt als (6)

Weitere Namen und Kennungen dieser Entität.

08

quellen

Welche Quellen diesen Datensatz belegen und wann.

09

Referenzen (3)

Externe Belege — Patches, Meldungen, Analysen.

scry

Angreifer nutzen Schwachstellen wie diese gegen im Internet exponierte Dienste aus. Sehen Sie mit einem kostenlosen Passiv-Scan, was exponiert ist.

Kostenloser Scan