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-24895 Microsoft.WindowsDesktop.…

HIGH

CVE-2023-24895 is a high-severity (CVSS 7.8) remote code execution vulnerability in Microsoft.WindowsDesktop.App.Runtime.win-arm64. A fix is available for Microsoft.WindowsDesktop.App.Runtime.win-arm64 — see the affected versions and patch details below.

.NET Remote Code Execution Vulnerability

Also known asBIT-dotnet-2023-24895BIT-dotnet-sdk-2023-24895GHSA-jh2h-qcrw-ghg7
Published
Jun 14, 2023
Updated
Jul 8, 2026
Affected
6 pkgs
Patched
6 / 6
Exploits
None indexed
Exploitation data as of Sep 18, 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-24895.

EPSS Exploitation Probability

via FIRST.org ↗
1.1%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs63th percentile — riskier than 63% 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-24895 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,166 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

6 pkgs affected
.NETMicrosoft.WindowsDesktop.App.Runtime.win-arm64.NETMicrosoft.WindowsDesktop.App.Runtime.win-x64.NETMicrosoft.WindowsDesktop.App.Runtime.win-x86.NETMicrosoft.WindowsDesktop.App.Runtime.win-arm64.NETMicrosoft.WindowsDesktop.App.Runtime.win-x64.NETMicrosoft.WindowsDesktop.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, .NET Framework, and Visual Studio Remote Code Execution Vulnerability

Affected Packages

6 total 6 fixed
EcosystemPackageVulnerable rangeFix
.NETNuGetMicrosoft.WindowsDesktop.App.Runtime.win-arm647.0.0&&< 7.0.77.0.7dotnet add package Microsoft.WindowsDesktop.App.Runtime.win-arm64 --version 7.0.7
.NETNuGetMicrosoft.WindowsDesktop.App.Runtime.win-x647.0.0&&< 7.0.77.0.7dotnet add package Microsoft.WindowsDesktop.App.Runtime.win-x64 --version 7.0.7
.NETNuGetMicrosoft.WindowsDesktop.App.Runtime.win-x867.0.0&&< 7.0.77.0.7dotnet add package Microsoft.WindowsDesktop.App.Runtime.win-x86 --version 7.0.7
.NETNuGetMicrosoft.WindowsDesktop.App.Runtime.win-arm646.0.0&&< 6.0.186.0.18dotnet add package Microsoft.WindowsDesktop.App.Runtime.win-arm64 --version 6.0.18
.NETNuGetMicrosoft.WindowsDesktop.App.Runtime.win-x646.0.0&&< 6.0.186.0.18dotnet add package Microsoft.WindowsDesktop.App.Runtime.win-x64 --version 6.0.18
.NETNuGetMicrosoft.WindowsDesktop.App.Runtime.win-x866.0.0&&< 6.0.186.0.18dotnet add package Microsoft.WindowsDesktop.App.Runtime.win-x86 --version 6.0.18

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

  2. Fix

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

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

Frequently Asked Questions

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

Is CVE-2023-24895 in your dependencies?

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

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