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-2023-21808 Microsoft.NetCore.App.Run…

HIGH

CVE-2023-21808 is a high-severity (CVSS 7.8) Use After Free vulnerability in Microsoft.NetCore.App.Runtime.win-arm. A fix is available for Microsoft.NetCore.App.Runtime.win-arm — see the affected versions and patch details below.

.NET Remote Code Execution Vulnerability

Also known asBIT-dotnet-2023-21808BIT-dotnet-sdk-2023-21808GHSA-824j-wqm8-89mj
Published
Feb 14, 2023
Updated
Aug 21, 2026
Affected
8 pkgs
Patched
8 / 8
Exploits
None indexed
Exploitation data as of Sep 20, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • A successful exploit gives an attacker total control of the affected component, not partial access.
  • 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-2023-21808.

EPSS Exploitation Probability

via FIRST.org ↗
1.1%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs65th percentile — riskier than 65% 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-2023-21808 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,333 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

8 pkgs affected
.NETMicrosoft.NetCore.App.Runtime.win-arm.NETMicrosoft.NetCore.App.Runtime.win-arm.NETMicrosoft.NetCore.App.Runtime.win-arm64.NETMicrosoft.NetCore.App.Runtime.win-arm64.NETMicrosoft.NetCore.App.Runtime.win-x64.NETMicrosoft.NetCore.App.Runtime.win-x64.NETMicrosoft.NetCore.App.Runtime.win-x86.NETMicrosoft.NetCore.App.Runtime.win-x86

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 and Visual Studio Remote Code Execution Vulnerability

Affected Packages

8 total 8 fixed
EcosystemPackageVulnerable rangeFix
.NETNuGetMicrosoft.NetCore.App.Runtime.win-arm7.0.0&&< 7.0.37.0.3dotnet add package Microsoft.NetCore.App.Runtime.win-arm --version 7.0.3
.NETNuGetMicrosoft.NetCore.App.Runtime.win-arm6.0.0&&< 6.0.146.0.14dotnet add package Microsoft.NetCore.App.Runtime.win-arm --version 6.0.14
.NETNuGetMicrosoft.NetCore.App.Runtime.win-arm647.0.0&&< 7.0.37.0.3dotnet add package Microsoft.NetCore.App.Runtime.win-arm64 --version 7.0.3
.NETNuGetMicrosoft.NetCore.App.Runtime.win-arm646.0.0&&< 6.0.146.0.14dotnet add package Microsoft.NetCore.App.Runtime.win-arm64 --version 6.0.14
.NETNuGetMicrosoft.NetCore.App.Runtime.win-x647.0.0&&< 7.0.37.0.3dotnet add package Microsoft.NetCore.App.Runtime.win-x64 --version 7.0.3
.NETNuGetMicrosoft.NetCore.App.Runtime.win-x646.0.0&&< 6.0.146.0.14dotnet add package Microsoft.NetCore.App.Runtime.win-x64 --version 6.0.14

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

  2. Fix

    Update Microsoft.NetCore.App.Runtime.win-arm to 7.0.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-21808 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-2023-21808 can be triaged on real exposure rather than presence alone.

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

Frequently Asked Questions

.NET and Visual Studio Remote Code Execution Vulnerability
O3 Security · Impact-Aware SCA

Is CVE-2023-21808 in your dependencies?

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

CVE-2023-21808: RCE (High 7.8) | O3 Security