Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
.NET NuGet

CVE-2018-0786

HIGH

CVE-2018-0786 is a high-severity (CVSS 7.5) CWE-295 vulnerability in Microsoft.NETCore.UniversalWindowsPlatform. O3 Security confirms whether CVE-2018-0786 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Improper Certificate Validation in Microsoft .NET Framework components

Also known asGHSA-jc8g-xhw5-6x46
Published
Jan 10, 2018
Updated
Jul 8, 2026
Affected
22 pkgs
Patched
22 / 22
Exploits
None indexed

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.UniversalWindowsPlatform5.2.0&&< 5.2.45.2.4
.NETNuGetMicrosoft.NETCore.UniversalWindowsPlatform5.3.0&&< 5.3.55.3.5
.NETNuGetMicrosoft.NETCore.UniversalWindowsPlatform5.4.0&&< 5.4.25.4.2
.NETNuGetMicrosoft.NETCore.UniversalWindowsPlatform6.0.0&&< 6.0.66.0.6
.NETNuGetSystem.ServiceModel.Primitives4.4.0&&< 4.4.14.4.1
.NETNuGetSystem.ServiceModel.Primitives4.3.0&&< 4.3.14.3.1

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

  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 CVE-2018-0786 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 pinpoints whether CVE-2018-0786 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 CVE-2018-0786. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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 CVE-2018-0786 in your dependencies?

O3 detects CVE-2018-0786 across NuGet dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.