Summary
Improper Certificate Validation in Microsoft .NET Framework components
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."
Impact
CVE-2018-0786 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (5.2.4, 5.3.5, 5.4.2, 6.0.6, 4.4.1, 4.3.1, 4.1.1, 4.0.2); upgrading removes the vulnerable code path.
Affected versions
Microsoft.NETCore.UniversalWindowsPlatform (>= 5.2.0, < 5.2.4)
Microsoft.NETCore.UniversalWindowsPlatform (>= 5.3.0, < 5.3.5)
Microsoft.NETCore.UniversalWindowsPlatform (>= 5.4.0, < 5.4.2)
Microsoft.NETCore.UniversalWindowsPlatform (>= 6.0.0, < 6.0.6)
System.ServiceModel.Primitives (= 4.4.0)
System.ServiceModel.Primitives (= 4.3.0)
System.ServiceModel.Primitives (= 4.1.0)
System.ServiceModel.Http (= 4.4.0)
System.ServiceModel.Http (= 4.3.0)
System.ServiceModel.Http (= 4.1.0)
System.ServiceModel.NetTcp (= 4.4.0)
System.ServiceModel.NetTcp (= 4.3.0)
System.ServiceModel.NetTcp (= 4.1.0)
System.ServiceModel.Duplex (= 4.4.0)
System.ServiceModel.Duplex (= 4.3.0)
System.ServiceModel.Security (= 4.4.0)
System.ServiceModel.Security (= 4.3.0)
System.Private.ServiceModel (= 4.4.0)
System.Private.ServiceModel (= 4.3.0)
System.Private.ServiceModel (= 4.1.0)
System.ServiceModel.Security (= 4.0.1)
System.ServiceModel.Duplex (= 4.0.1)
Security releases
Microsoft.NETCore.UniversalWindowsPlatform → 5.2.4 (nuget)
Microsoft.NETCore.UniversalWindowsPlatform → 5.3.5 (nuget)
Microsoft.NETCore.UniversalWindowsPlatform → 5.4.2 (nuget)
Microsoft.NETCore.UniversalWindowsPlatform → 6.0.6 (nuget)
System.ServiceModel.Primitives → 4.4.1 (nuget)
System.ServiceModel.Primitives → 4.3.1 (nuget)
System.ServiceModel.Primitives → 4.1.1 (nuget)
System.ServiceModel.Http → 4.4.1 (nuget)
System.ServiceModel.Http → 4.3.1 (nuget)
System.ServiceModel.Http → 4.1.1 (nuget)
System.ServiceModel.NetTcp → 4.4.1 (nuget)
System.ServiceModel.NetTcp → 4.3.1 (nuget)
System.ServiceModel.NetTcp → 4.1.1 (nuget)
System.ServiceModel.Duplex → 4.4.1 (nuget)
System.ServiceModel.Duplex → 4.3.1 (nuget)
System.ServiceModel.Security → 4.4.1 (nuget)
System.ServiceModel.Security → 4.3.1 (nuget)
System.Private.ServiceModel → 4.4.1 (nuget)
System.Private.ServiceModel → 4.3.1 (nuget)
System.Private.ServiceModel → 4.1.1 (nuget)
System.ServiceModel.Security → 4.0.2 (nuget)
System.ServiceModel.Duplex → 4.0.2 (nuget)
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Upgrade the following packages to resolve this vulnerability:
Microsoft.NETCore.UniversalWindowsPlatform to 5.2.4 or later; Microsoft.NETCore.UniversalWindowsPlatform to 5.3.5 or later; Microsoft.NETCore.UniversalWindowsPlatform to 5.4.2 or later; Microsoft.NETCore.UniversalWindowsPlatform to 6.0.6 or later; System.ServiceModel.Primitives to 4.4.1 or later; System.ServiceModel.Primitives to 4.3.1 or later; System.ServiceModel.Primitives to 4.1.1 or later; System.ServiceModel.Http to 4.4.1 or later; System.ServiceModel.Http to 4.3.1 or later; System.ServiceModel.Http to 4.1.1 or later; System.ServiceModel.NetTcp to 4.4.1 or later; System.ServiceModel.NetTcp to 4.3.1 or later; System.ServiceModel.NetTcp to 4.1.1 or later; System.ServiceModel.Duplex to 4.4.1 or later; System.ServiceModel.Duplex to 4.3.1 or later; System.ServiceModel.Security to 4.4.1 or later; System.ServiceModel.Security to 4.3.1 or later; System.Private.ServiceModel to 4.4.1 or later; System.Private.ServiceModel to 4.3.1 or later; System.Private.ServiceModel to 4.1.1 or later; System.ServiceModel.Security to 4.0.2 or later; System.ServiceModel.Duplex to 4.0.2 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Microsoft.NETCore.UniversalWindowsPlatform to 5.2.4 or later; Microsoft.NETCore.UniversalWindowsPlatform to 5.3.5 or later; Microsoft.NETCore.UniversalWindowsPlatform to 5.4.2 or later; Microsoft.NETCore.UniversalWindowsPlatform to 6.0.6 or later; System.ServiceModel.Primitives to 4.4.1 or later; System.ServiceModel.Primitives to 4.3.1 or later; System.ServiceModel.Primitives to 4.1.1 or later; System.ServiceModel.Http to 4.4.1 or later; System.ServiceModel.Http to 4.3.1 or later; System.ServiceModel.Http to 4.1.1 or later; System.ServiceModel.NetTcp to 4.4.1 or later; System.ServiceModel.NetTcp to 4.3.1 or later; System.ServiceModel.NetTcp to 4.1.1 or later; System.ServiceModel.Duplex to 4.4.1 or later; System.ServiceModel.Duplex to 4.3.1 or later; System.ServiceModel.Security to 4.4.1 or later; System.ServiceModel.Security to 4.3.1 or later; System.Private.ServiceModel to 4.4.1 or later; System.Private.ServiceModel to 4.3.1 or later; System.Private.ServiceModel to 4.1.1 or later; System.ServiceModel.Security to 4.0.2 or later; System.ServiceModel.Duplex to 4.0.2 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2018-0786? CVE-2018-0786 is a high-severity security vulnerability in Microsoft.NETCore.UniversalWindowsPlatform (nuget), affecting versions >= 5.2.0, < 5.2.4. It is fixed in 5.2.4, 5.3.5, 5.4.2, 6.0.6, 4.4.1, 4.3.1, 4.1.1, 4.0.2.
- How severe is CVE-2018-0786? CVE-2018-0786 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which packages are affected by CVE-2018-0786?
Microsoft.NETCore.UniversalWindowsPlatform(nuget) (versions >= 5.2.0, < 5.2.4)System.ServiceModel.Primitives(nuget) (versions = 4.4.0)System.ServiceModel.Http(nuget) (versions = 4.4.0)System.ServiceModel.NetTcp(nuget) (versions = 4.4.0)System.ServiceModel.Duplex(nuget) (versions = 4.4.0)System.ServiceModel.Security(nuget) (versions = 4.4.0)System.Private.ServiceModel(nuget) (versions = 4.4.0)
- Is there a fix for CVE-2018-0786? Yes. CVE-2018-0786 is fixed in 5.2.4, 5.3.5, 5.4.2, 6.0.6, 4.4.1, 4.3.1, 4.1.1, 4.0.2. Upgrade to this version or later.
- Is CVE-2018-0786 exploitable, and should I be worried? Whether CVE-2018-0786 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2018-0786 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2018-0786?
- Upgrade
Microsoft.NETCore.UniversalWindowsPlatformto 5.2.4 or later - Upgrade
Microsoft.NETCore.UniversalWindowsPlatformto 5.3.5 or later - Upgrade
Microsoft.NETCore.UniversalWindowsPlatformto 5.4.2 or later - Upgrade
Microsoft.NETCore.UniversalWindowsPlatformto 6.0.6 or later - Upgrade
System.ServiceModel.Primitivesto 4.4.1 or later - Upgrade
System.ServiceModel.Primitivesto 4.3.1 or later - Upgrade
System.ServiceModel.Primitivesto 4.1.1 or later - Upgrade
System.ServiceModel.Httpto 4.4.1 or later - Upgrade
System.ServiceModel.Httpto 4.3.1 or later - Upgrade
System.ServiceModel.Httpto 4.1.1 or later - Upgrade
System.ServiceModel.NetTcpto 4.4.1 or later - Upgrade
System.ServiceModel.NetTcpto 4.3.1 or later - Upgrade
System.ServiceModel.NetTcpto 4.1.1 or later - Upgrade
System.ServiceModel.Duplexto 4.4.1 or later - Upgrade
System.ServiceModel.Duplexto 4.3.1 or later - Upgrade
System.ServiceModel.Securityto 4.4.1 or later - Upgrade
System.ServiceModel.Securityto 4.3.1 or later - Upgrade
System.Private.ServiceModelto 4.4.1 or later - Upgrade
System.Private.ServiceModelto 4.3.1 or later - Upgrade
System.Private.ServiceModelto 4.1.1 or later - Upgrade
System.ServiceModel.Securityto 4.0.2 or later - Upgrade
System.ServiceModel.Duplexto 4.0.2 or later
- Upgrade