Breaking News: Thousands Of GitHub Accounts Hijacked With wfx-loot CI Secret
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2026-40372

ASP.NET Core: ASP.NET: ASP.NET Core: Privilege escalation via improper cryptographic signature verification

Overview

Published
21 Apr 2026
Modified
26 Oct 2026
Critical CVE
2 Registry packages
25 OS packages
3 Linux distributions
Yes Fix available

Description

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

Source: OX vulnerability database

Severity

9.1 · CRITICAL

CVSS 3.1 base score, scored by NVD.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Weakness: CWE-347

Affected packages · 2

Packages affected by CVE-2026-40372
EcosystemPackageVulnerableFixed in
Bitnami aspnet-core >=10.0.0, <10.0.7 10.0.7
NuGet Microsoft.AspNetCore.DataProtection >=10.0.0, <10.0.7 10.0.7

Open a package to see all its vulnerabilities.

Operating systems · 7 fixes

alpine 3 releases · 1 package

fixed 3
dotnet10-runtime
alpine fixes for CVE-2026-40372
ReleasePackageFixed in
3.23 dotnet10-runtime 10.0.7-r0
3.24 dotnet10-runtime 10.0.7-r0
edge dotnet10-runtime 10.0.7-r0

amazon linux 1 release · 2 packages

fixed 2
dotnet aspnetcore-runtime-10-0
amazon linux fixes for CVE-2026-40372
ReleasePackageFixed in
2023 dotnet +9 10.0.107-1.amzn2023.0.1
2023 aspnetcore-runtime-10-0 +12 10.0.7-1.amzn2023.0.1

ubuntu 2 releases · 1 package

fixed 2
dotnet10
ubuntu fixes for CVE-2026-40372
ReleasePackageFixed in
24.04 dotnet10 10.0.107-10.0.7-0ubuntu1~24.04.1
26.04 dotnet10 10.0.107-10.0.7-0ubuntu1~26.04.1

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.