GHSA-vh55-786g-wjwj
MEDIUM.NET Information Disclosure Vulnerability
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Blast Radius
System.Security.Cryptography.Xml.NETSystem.Security.Cryptography.Xml.NETMicrosoft.AspNetCore.App.Runtime.win-x64.NETMicrosoft.AspNetCore.App.Runtime.win-x64.NETMicrosoft.AspNetCore.App.Runtime.linux-x64.NETMicrosoft.AspNetCore.App.Runtime.linux-x64.NETMicrosoft.AspNetCore.App.Runtime.win-x86.NETMicrosoft.AspNetCore.App.Runtime.win-x86+17 moreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.
Description
Microsoft is releasing this security advisory to provide information about a vulnerability in .NET Core 3.1 and .NET 6.0. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability.
An information disclosure vulnerability exists in .NET Core 3.1 and .NET 6.0 that could lead to unauthorized access of privileged information.
<a name="affected-software"></a>Affected software
- Any .NET 6.0 application running on .NET 6.0.7 or earlier.
- Any .NET Core 3.1 applicaiton running on .NET Core 3.1.27 or earlier.
If your application uses the following package versions, ensure you update to the latest version of .NET.
<a name=".NET Core 3.1"></a>.NET Core 3.1
| Package name | Affected version | Patched version |
|---|---|---|
| System.Security.Cryptography.Xml | <=4.7.0 | 4.7.1 |
| Microsoft.AspNetCore.App.Runtime.win-x64 | >=3.1.0, 3.1.27 | 3.1.28 |
| Microsoft.AspNetCore.App.Runtime.linux-x64 | >=3.1.0, 3.1.27 | 3.1.28 |
| Microsoft.AspNetCore.App.Runtime.win-x86 | >=3.1.0, 3.1.27 | 3.1.28 |
| Microsoft.AspNetCore.App.Runtime.osx-x64 | >=3.1.0, 3.1.27 | 3.1.28 |
| Microsoft.AspNetCore.App.Runtime.linux-musl-x64 | >=3.1.0, 3.1.27 | 3.1.28 |
| Microsoft.AspNetCore.App.Runtime.linux-arm64 | >=3.1.0, 3.1.27 | 3.1.28 |
| Microsoft.AspNetCore.App.Runtime.linux-arm | >=3.1.0, 3.1.27 | 3.1.28 |
| Microsoft.AspNetCore.App.Runtime.win-arm64 | >=3.1.0, 3.1.27 | 3.1.28 |
| Microsoft.AspNetCore.App.Runtime.win-arm | >=3.1.0, 3.1.27 | 3.1.28 |
| Microsoft.AspNetCore.App.Runtime.linux-musl-arm64 | >=3.1.0, 3.1.27 | 3.1.28 |
| Microsoft.AspNetCore.App.Runtime.linux-musl-arm | >=3.1.0, 3.1.27 | 3.1.28 |
<a name=".NET 6"></a>.NET 6
| Package name | Affected version | Patched version |
|---|---|---|
| System.Security.Cryptography.Xml | >=5.0.0, 6.0.0 | 6.0.1 |
| Microsoft.AspNetCore.App.Runtime.win-x64 | >=6.0.0, 6.0.7 | 6.0.8 |
| Microsoft.AspNetCore.App.Runtime.linux-x64 | >=6.0.0, 6.0.7 | 6.0.8 |
| Microsoft.AspNetCore.App.Runtime.win-x86 | >=6.0.0, 6.0.7 | 6.0.8 |
| Microsoft.AspNetCore.App.Runtime.osx-x64 | >=6.0.0, 6.0.7 | 6.0.8 |
| Microsoft.AspNetCore.App.Runtime.linux-musl-x64 | >=6.0.0, 6.0.7 | 6.0.8 |
| Microsoft.AspNetCore.App.Runtime.linux-arm64 | >=6.0.0, 6.0.7 | 6.0.8 |
| Microsoft.AspNetCore.App.Runtime.linux-arm | >=6.0.0, 6.0.7 | 6.0.8 |
| Microsoft.AspNetCore.App.Runtime.win-arm64 | >=6.0.0, 6.0.7 | 6.0.8 |
| Microsoft.AspNetCore.App.Runtime.win-arm | >=6.0.0, 6.0.7 | 6.0.8 |
| Microsoft.AspNetCore.App.Runtime.osx-arm64 | >=6.0.0, 6.0.7 | 6.0.8 |
| Microsoft.AspNetCore.App.Runtime.linux-musl-arm64 | >=6.0.0, 6.0.7 | 6.0.8 |
| Microsoft.AspNetCore.App.Runtime.linux-musl-arm | >=6.0.0, 6.0.7 | 6.0.8 |
Patches
- If you're using .NET 6.0, you should download and install Runtime 6.0.8 or SDK 6.0.108 (for Visual Studio 2022 v17.1) from https://dotnet.microsoft.com/download/dotnet-core/6.0.
- If you're using .NET Core 3.1, you should download and install Runtime 3.1.28 (for Visual Studio 2019 v16.9) from https://dotnet.microsoft.com/download/dotnet-core/3.1.
Other
Announcement for this issue can be found at https://github.com/dotnet/announcements/issues/232 An Issue for this can be found at https://github.com/dotnet/aspnetcore/issues/43166 MSRC details for this can be found at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2022-34716
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| .NETNuGet | System.Security.Cryptography.Xml | all versions | 4.7.1 |
| .NETNuGet | System.Security.Cryptography.Xml | ≥ 5.0.0&&< 6.0.1 | 6.0.1 |
| .NETNuGet | Microsoft.AspNetCore.App.Runtime.win-x64 | ≥ 3.1.0&&< 3.1.28 | 3.1.28 |
| .NETNuGet | Microsoft.AspNetCore.App.Runtime.win-x64 | ≥ 6.0.0&&< 6.0.8 | 6.0.8 |
| .NETNuGet | Microsoft.AspNetCore.App.Runtime.linux-x64 | ≥ 3.1.0&&< 3.1.28 | 3.1.28 |
| .NETNuGet | Microsoft.AspNetCore.App.Runtime.linux-x64 | ≥ 6.0.0&&< 6.0.8 | 6.0.8 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for System.Security.Cryptography.Xml. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update System.Security.Cryptography.Xml to 4.7.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vh55-786g-wjwj is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-vh55-786g-wjwj is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-vh55-786g-wjwj. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-vh55-786g-wjwj in your dependencies?
O3 detects GHSA-vh55-786g-wjwj across NuGet dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.