Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
.NET
.NET NuGet
Not in CISA KEV
HIGH severity

CVE-2021-26423 Microsoft.NETCore.App.Run…

HIGH

CVE-2021-26423 is a high-severity (CVSS 7.5) vulnerability in Microsoft.NETCore.App.Runtime.win-x86. A fix is available for Microsoft.NETCore.App.Runtime.win-x86 — see the affected versions and patch details below.

.NET Core Elevation of Privilege Vulnerability

Also known asBIT-dotnet-2021-26423BIT-dotnet-sdk-2021-26423GHSA-rh58-r7jh-xhx3
Published
Aug 12, 2021
Updated
Sep 14, 2026
Affected
33 pkgs
Patched
33 / 33
Exploits
None indexed
Exploitation data as of Sep 18, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2021-26423.

EPSS Exploitation Probability

via FIRST.org ↗
3.9%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs90th percentile — riskier than 90% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

CVE-2021-26423 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 377,238 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

33 pkgs affected
.NETMicrosoft.NETCore.App.Runtime.win-x86.NETMicrosoft.NETCore.App.Runtime.win-x86.NETMicrosoft.NETCore.App.Runtime.win-x64.NETMicrosoft.NETCore.App.Runtime.win-x64.NETMicrosoft.NETCore.App.Runtime.win-arm64.NETMicrosoft.NETCore.App.Runtime.win-arm64.NETMicrosoft.NETCore.App.Runtime.win-arm.NETMicrosoft.NETCore.App.Runtime.win-arm+25 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

.NET Core and Visual Studio Denial of Service Vulnerability

Affected Packages

33 total 33 fixed
EcosystemPackageVulnerable rangeFix
.NETNuGetMicrosoft.NETCore.App.Runtime.win-x863.1.0&&< 3.1.183.1.18dotnet add package Microsoft.NETCore.App.Runtime.win-x86 --version 3.1.18
.NETNuGetMicrosoft.NETCore.App.Runtime.win-x865.0.0&&< 5.0.95.0.9dotnet add package Microsoft.NETCore.App.Runtime.win-x86 --version 5.0.9
.NETNuGetMicrosoft.NETCore.App.Runtime.win-x643.1.0&&< 3.1.183.1.18dotnet add package Microsoft.NETCore.App.Runtime.win-x64 --version 3.1.18
.NETNuGetMicrosoft.NETCore.App.Runtime.win-x645.0.0&&< 5.0.95.0.9dotnet add package Microsoft.NETCore.App.Runtime.win-x64 --version 5.0.9
.NETNuGetMicrosoft.NETCore.App.Runtime.win-arm643.1.0&&< 3.1.183.1.18dotnet add package Microsoft.NETCore.App.Runtime.win-arm64 --version 3.1.18
.NETNuGetMicrosoft.NETCore.App.Runtime.win-arm645.0.0&&< 5.0.95.0.9dotnet add package Microsoft.NETCore.App.Runtime.win-arm64 --version 5.0.9

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.App.Runtime.win-x86, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update Microsoft.NETCore.App.Runtime.win-x86 to 3.1.18 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-26423 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2021-26423 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2021-26423. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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 HatImportant
ProductFixed inAdvisory
.NET Core on Red Hat Enterprise Linuxrh-dotnet31-dotnet-0:3.1.118-1.el7_9RHSA-2021:3143
.NET Core on Red Hat Enterprise Linuxrh-dotnet50-dotnet-0:5.0.206-1.el7_9RHSA-2021:3147
Red Hat Enterprise Linux 8dotnet3.1-0:3.1.118-1.el8_4RHSA-2021:3142
Red Hat Enterprise Linux 8dotnet5.0-0:5.0.206-1.el8_4RHSA-2021:3148

Frequently Asked Questions

.NET Core and Visual Studio Denial of Service Vulnerability
O3 Security · Impact-Aware SCA

Is CVE-2021-26423 in your dependencies?

O3 Security finds CVE-2021-26423 across NuGet dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

CVE-2021-26423: DoS (High 7.5) | O3 Security