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

CVE-2018-8356 — System.Private.ServiceMod…

MEDIUM

CVE-2018-8356 is a medium-severity (CVSS 5.5) CWE-295 vulnerability in System.Private.ServiceModel. A fix is available for System.Private.ServiceModel — see the affected versions and patch details below.

Improper Certificate Validation in Microsoft .NET Framework components

Also known asGHSA-p9wx-v264-q34p
Published
Updated
Affected
24 pkgs
Patched
24 / 24
Exploits
None indexed
Exploitation data as of Oct 29, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.7%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs55th percentile — riskier than 55% of all scored CVEsHighest risk
0.00%0.42%0.83%1.25%0.2%0.7%Apr 26Aug 26Oct 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

24 pkgs affected
.NETSystem.Private.ServiceModel.NETSystem.Private.ServiceModel.NETSystem.Private.ServiceModel.NETSystem.Private.ServiceModel.NETSystem.ServiceModel.Duplex.NETSystem.ServiceModel.Duplex.NETSystem.ServiceModel.Duplex.NETSystem.ServiceModel.Duplex+16 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

A security feature bypass vulnerability exists when Microsoft .NET Framework components do not correctly validate certificates, aka ".NET Framework Security Feature Bypass Vulnerability." This affects .NET Framework 4.7.2, Microsoft .NET Framework 3.0, Microsoft .NET Framework 4.6.2/4.7/4.7.1/4.7.2, ASP.NET Core 1.1, Microsoft .NET Framework 4.5.2, ASP.NET Core 2.0, ASP.NET Core 1.0, .NET Core 1.1, Microsoft .NET Framework 3.5, Microsoft .NET Framework 3.5.1, Microsoft .NET Framework 4.6/4.6.1/4.6.2, .NET Core 1.0, .NET Core 2.0, Microsoft .NET Framework 4.6, Microsoft .NET Framework 4.6/4.6.1/4.6.2/4.7/4.7.1/4.7.1/4.7.2, Microsoft .NET Framework 4.7.2.

Affected Packages

24 total 24 fixed
EcosystemPackageVulnerable rangeFix
.NETNuGetSystem.Private.ServiceModel≥ 4.0.0&&< 4.1.34.1.3dotnet add package System.Private.ServiceModel --version 4.1.3
.NETNuGetSystem.Private.ServiceModel≥ 4.3.0&&< 4.3.34.3.3dotnet add package System.Private.ServiceModel --version 4.3.3
.NETNuGetSystem.Private.ServiceModel≥ 4.4.0&&< 4.4.44.4.4dotnet add package System.Private.ServiceModel --version 4.4.4
.NETNuGetSystem.Private.ServiceModel≥ 4.5.0&&< 4.5.34.5.3dotnet add package System.Private.ServiceModel --version 4.5.3
.NETNuGetSystem.ServiceModel.Duplex≥ 4.3.0&&< 4.3.34.3.3dotnet add package System.ServiceModel.Duplex --version 4.3.3
.NETNuGetSystem.ServiceModel.Duplex≥ 4.4.0&&< 4.4.44.4.4dotnet add package System.ServiceModel.Duplex --version 4.4.4

Affected Products

5 products · 28 configurations
Application
.net coremicrosoft
3 versions
1.01.12.0
Application
.net frameworkmicrosoft
10 versions
3.03.53.5.14.5.24.64.6.14.6.24.74.7.14.7.2
Application
.net framework developer packmicrosoft
1 version
4.7.2
Application
asp.net coremicrosoft
3 versions
1.01.12.0
Application
powershell coremicrosoft
2 versions
6.06.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 System.Private.ServiceModel, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update System.Private.ServiceModel to 4.1.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-8356 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

A security feature bypass vulnerability exists when Microsoft .NET Framework components do not correctly validate certificates, aka ".NET Framework Security Feature Bypass Vulnerability." This affects .NET Framework 4.7.2, Microsoft .NET Framework 3.0, Microsoft .NET Framework 4.6.2/4.7/4.7.1/4.7.2, ASP.NET Core 1.1, Microsoft .NET Framework 4.5.2, ASP.NET Core 2.0, ASP.NET Core 1.0, .NET Core 1.1, Microsoft .NET Framework 3.5, Microsoft .NET Framework 3.5.1, Microsoft .NET Framework 4.6/4.6.1/4.6.2, .NET Core 1.0, .NET Core 2.0, Microsoft .NET Framework 4.6, Microsoft .NET Framework 4.6/4.6.1
O3 Security · Impact-Aware SCA

Is CVE-2018-8356 in your dependencies?

Find it across NuGet, including transitive dependencies.

CVE-2018-8356: System.Private — Fixed in 4.1.3