Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
.NET NuGet

CVE-2026-40372

CRITICAL

CVE-2026-40372 is a critical-severity (CVSS 9.1) CWE-347 vulnerability in Microsoft.AspNetCore.DataProtection. O3 Security confirms whether CVE-2026-40372 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Microsoft Security Advisory CVE-2026-40372 – ASP.NET Core Elevation of Privilege

Also known asBIT-aspnet-core-2026-40372GHSA-9mv3-2cwr-p262
Published
Apr 21, 2026
Updated
Jul 22, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed

Real-World Exposure

1 pkg affected
.NETMicrosoft.AspNetCore.DataProtection

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

Improper verification of cryptographic signature in ASP.NET Core allows an unauthorized attacker to elevate privileges over a network.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
.NETNuGetMicrosoft.AspNetCore.DataProtection10.0.0&&< 10.0.710.0.7

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.AspNetCore.DataProtection. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update Microsoft.AspNetCore.DataProtection to 10.0.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-40372 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 pinpoints whether CVE-2026-40372 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

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

Frequently Asked Questions

Improper verification of cryptographic signature in ASP.NET Core allows an unauthorized attacker to elevate privileges over a network.
O3 Security · Impact-Aware SCA

Is CVE-2026-40372 in your dependencies?

O3 detects CVE-2026-40372 across NuGet dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.