How severe is CVE-2018-0875?

CVE-2018-0875 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2018-0875?

CVE-2018-0875 affects the following packages: Microsoft.NETCore.Jit (NuGet), Microsoft.NETCore.Jit (NuGet), Microsoft.NETCore.Jit (NuGet). Ecosystems affected: NuGet.

How do I fix CVE-2018-0875?

Update Microsoft.NETCore.Jit to 2.0.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-0875 is resolved across your whole dependency graph.

How do I detect CVE-2018-0875 in my NuGet dependencies?

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

How do I mitigate CVE-2018-0875 if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is CVE-2018-0875 actively exploited in the wild?

No public exploit code has been indexed for CVE-2018-0875 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2018-0875?

CVE-2018-0875 has an EPSS (Exploit Prediction Scoring System) score of 9.1%, placing it in the 95th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was CVE-2018-0875 published, and has it been updated?

CVE-2018-0875 was published on March 14, 2018 and was last updated on October 24, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

.NET

.NET NuGet

Not in CISA KEV

HIGH severity

CVE-2018-0875 — Microsoft.NETCore.Jit

HIGH

CVE-2018-0875 is a high-severity (CVSS 7.5) vulnerability in Microsoft.NETCore.Jit. A fix is available for Microsoft.NETCore.Jit — see the affected versions and patch details below.

.NET Core Denial of Service Vulnerability

Also known asGHSA-xcvr-qv8h-m7xw

Published

Mar 14, 2018

Updated

Oct 24, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

9.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs95th percentile — riskier than 95% of all scored CVEsHighest risk

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

3 pkgs affected

.NETMicrosoft.NETCore.Jit.NETMicrosoft.NETCore.Jit.NETMicrosoft.NETCore.Jit

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

.NET Core 1.0, .NET Core 1.1, NET Core 2.0 and PowerShell Core 6.0.0 allow a denial of Service vulnerability due to how specially crafted requests are handled, aka ".NET Core Denial of Service Vulnerability".

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
.NETNuGet	`Microsoft.NETCore.Jit`	≥ 2.0.0&&< 2.0.6	2.0.6`dotnet add package Microsoft.NETCore.Jit --version 2.0.6`
.NETNuGet	`Microsoft.NETCore.Jit`	≥ 1.1.0&&< 1.1.7	1.1.7`dotnet add package Microsoft.NETCore.Jit --version 1.1.7`
.NETNuGet	`Microsoft.NETCore.Jit`	all versions	1.0.12`dotnet add package Microsoft.NETCore.Jit --version 1.0.12`

Affected Products

2 products · 4 configurations

Application

asp.net coremicrosoft

3 versions

1.01.12.0

Application

powershell coremicrosoft

1 version

6.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Microsoft.NETCore.Jit, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update Microsoft.NETCore.Jit to 2.0.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-0875 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

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 HatLow

Product	Fixed in	Advisory
.NET Core on Red Hat Enterprise Linux	`rh-dotnet20-dotnet-0:2.0.6-1.el7`	RHSA-2018:0522

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2018-0875 in your dependencies?

Find it across NuGet, including transitive dependencies.

Scan my dependencies How O3 SCA works