Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
.NET
.NET NuGet
Not in CISA KEV
MEDIUM severity

GHSA-vh55-786g-wjwj System.Security.Cryptogra…

MEDIUM

GHSA-vh55-786g-wjwj is a medium-severity (CVSS 5.9) CWE-290 vulnerability in System.Security.Cryptography.Xml. A fix is available for System.Security.Cryptography.Xml — see the affected versions and patch details below.

.NET Information Disclosure Vulnerability

Also known asBIT-dotnet-2022-34716BIT-dotnet-sdk-2022-34716BIT-powershell-2022-34716CVE-2022-34716
Published
Feb 3, 2024
Updated
Sep 4, 2025
Affected
25 pkgs
Patched
25 / 25
Exploits
None indexed
Exploitation data as of Sep 17, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-vh55-786g-wjwj.

EPSS Exploitation Probability

via FIRST.org ↗
2.3%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs82th percentile — riskier than 82% of all scored CVEsHighest risk

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.

How urgent is this, really

GHSA-vh55-786g-wjwj plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 377,166 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

25 pkgs affected
.NETSystem.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 more

Real-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

<a name=".NET 6"></a>.NET 6

Patches

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

25 total 25 fixed
EcosystemPackageVulnerable rangeFix
.NETNuGetSystem.Security.Cryptography.Xmlall versions4.7.1dotnet add package System.Security.Cryptography.Xml --version 4.7.1
.NETNuGetSystem.Security.Cryptography.Xml5.0.0&&< 6.0.16.0.1dotnet add package System.Security.Cryptography.Xml --version 6.0.1
.NETNuGetMicrosoft.AspNetCore.App.Runtime.win-x643.1.0&&< 3.1.283.1.28dotnet add package Microsoft.AspNetCore.App.Runtime.win-x64 --version 3.1.28
.NETNuGetMicrosoft.AspNetCore.App.Runtime.win-x646.0.0&&< 6.0.86.0.8dotnet add package Microsoft.AspNetCore.App.Runtime.win-x64 --version 6.0.8
.NETNuGetMicrosoft.AspNetCore.App.Runtime.linux-x643.1.0&&< 3.1.283.1.28dotnet add package Microsoft.AspNetCore.App.Runtime.linux-x64 --version 3.1.28
.NETNuGetMicrosoft.AspNetCore.App.Runtime.linux-x646.0.0&&< 6.0.86.0.8dotnet add package Microsoft.AspNetCore.App.Runtime.linux-x64 --version 6.0.8

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for System.Security.Cryptography.Xml, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. 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.

  3. 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.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-vh55-786g-wjwj can be triaged on real exposure rather than presence alone.

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.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate
ProductFixed inAdvisory
.NET Core on Red Hat Enterprise Linuxrh-dotnet31-dotnet-0:3.1.422-1.el7_9RHSA-2022:6037
.NET Core on Red Hat Enterprise Linuxrh-dotnet60-dotnet-0:6.0.108-1.el7_9RHSA-2022:6038
Red Hat Enterprise Linux 8dotnet3.1-0:3.1.422-1.el8_6RHSA-2022:6057
Red Hat Enterprise Linux 8dotnet6.0-0:6.0.108-1.el8_6RHSA-2022:6058
Red Hat Enterprise Linux 9dotnet6.0-0:6.0.108-1.el9_0RHSA-2022:6043

Frequently Asked Questions

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 use
O3 Security · Impact-Aware SCA

Is GHSA-vh55-786g-wjwj in your dependencies?

O3 Security finds GHSA-vh55-786g-wjwj across NuGet dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

GHSA-vh55-786g-wjwj: Medium 5.9 severity | O3 Security