NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
.NET
.NET NuGet
Not in CISA KEV
HIGH severity

Improper Certificate Validation in Microsoft .NET Framework componentsGHSA-jc8g-xhw5-6x46

HIGH

GHSA-jc8g-xhw5-6x46 is a high-severity (CVSS 7.5) CWE-295 vulnerability in Microsoft.NETCore.UniversalWindowsPlatform. A fix is available for Microsoft.NETCore.UniversalWindowsPlatform — see the affected versions and patch details below.

Also known asCVE-2018-0786
Published
Updated
Affected
22 pkgs
Patched
22 / 22
Exploits
None indexed
Exploitation data as of Nov 11, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
3.7%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs90th percentile — riskier than 90% of all scored CVEsHighest risk
1.53%2.41%3.30%4.19%2.0%3.7%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

22 pkgs affected
.NETMicrosoft.NETCore.UniversalWindowsPlatform.NETMicrosoft.NETCore.UniversalWindowsPlatform.NETMicrosoft.NETCore.UniversalWindowsPlatform.NETMicrosoft.NETCore.UniversalWindowsPlatform.NETSystem.ServiceModel.Primitives.NETSystem.ServiceModel.Primitives.NETSystem.ServiceModel.Primitives.NETSystem.ServiceModel.Http+14 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 .NET Framework 2.0 SP2, 3.0 SP2, 3.5, 3.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, .NET Core 1.0 and 2.0, and PowerShell Core 6.0.0 allow a security feature bypass vulnerability due to the way certificates are validated, aka ".NET Security Feature Bypass Vulnerability."

Affected Packages

22 total 22 fixed
EcosystemPackageVulnerable rangeFix
.NETNuGetMicrosoft.NETCore.UniversalWindowsPlatform≥ 5.2.0&&< 5.2.45.2.4dotnet add package Microsoft.NETCore.UniversalWindowsPlatform --version 5.2.4
.NETNuGetMicrosoft.NETCore.UniversalWindowsPlatform≥ 5.3.0&&< 5.3.55.3.5dotnet add package Microsoft.NETCore.UniversalWindowsPlatform --version 5.3.5
.NETNuGetMicrosoft.NETCore.UniversalWindowsPlatform≥ 5.4.0&&< 5.4.25.4.2dotnet add package Microsoft.NETCore.UniversalWindowsPlatform --version 5.4.2
.NETNuGetMicrosoft.NETCore.UniversalWindowsPlatform≥ 6.0.0&&< 6.0.66.0.6dotnet add package Microsoft.NETCore.UniversalWindowsPlatform --version 6.0.6
.NETNuGetSystem.ServiceModel.Primitives≥ 4.4.0&&< 4.4.14.4.1dotnet add package System.ServiceModel.Primitives --version 4.4.1
.NETNuGetSystem.ServiceModel.Primitives≥ 4.3.0&&< 4.3.14.3.1dotnet add package System.ServiceModel.Primitives --version 4.3.1

Affected Products

3 products · 18 configurations
Application
.net coremicrosoft
2 versions
1.02.0
Application
.net frameworkmicrosoft
10 versions
2.03.03.53.5.14.5.24.64.6.14.6.24.74.7.1
Application
powershell coremicrosoft
1 version
6.0

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Fix

    Update Microsoft.NETCore.UniversalWindowsPlatform to 5.2.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jc8g-xhw5-6x46 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.

Frequently Asked Questions

Microsoft .NET Framework 2.0 SP2, 3.0 SP2, 3.5, 3.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, .NET Core 1.0 and 2.0, and PowerShell Core 6.0.0 allow a security feature bypass vulnerability due to the way certificates are validated, aka ".NET Security Feature Bypass Vulnerability."
O3 Security · Impact-Aware SCA

Is GHSA-jc8g-xhw5-6x46 in your dependencies?

Find it across NuGet, including transitive dependencies.

Scan my dependencies How O3 SCA works
Improper Certificate Validation in Microsoft .NET…