cve.bz

CVE-2026-40372 microsoft asp.net core

9.1 criticalEPSS 11%Fix available

Critical (9.1) in microsoft asp.net core. EPSS 11% estimated probability of exploitation activity in the next 30 days. Fixed in Microsoft.AspNetCore.DataProtection 10.0.7.

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

Severity

CVSS 3.1

9.1 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS
11% (unchanged from 11% a week ago; 0.8% 30 days ago) estimated probability of exploitation activity in the next 30 days; 96th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: total, assessed 2026-04-21. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-347 Improper Verification of Cryptographic Signature
OWASP Top 10
A04:2025 Cryptographic Failures
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-40372 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-40372?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-40372?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-40372 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-40372

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-40372](https://cve.bz/cve/badge/CVE-2026-40372.svg)](https://cve.bz/cve/CVE-2026-40372)

HTML:

<a href="https://cve.bz/cve/CVE-2026-40372"><img src="https://cve.bz/cve/badge/CVE-2026-40372.svg" alt="CVE-2026-40372"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Microsoft ASP.NET Core 10.0from 10.0 before 10.0.7
Microsoft Visual Studio 2026 version 18.5from 18.5.0 before 18.5.2

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-9mv3-2cwr-p262NuGetMicrosoft.AspNetCore.DataProtection>=10.0.0 <10.0.710.0.7

Linux distributions

DistributionReleasePackageFixed inAdvisory
Ubuntu22.04:LTSdotnet7no fix listedUBUNTU-CVE-2026-40372
Ubuntu24.04:LTSdotnet1010.0.107-10.0.7-0ubuntu1~24.04.1UBUNTU-CVE-2026-40372
Ubuntu25.10dotnet1010.0.107-10.0.7-0ubuntu1~25.10.1UBUNTU-CVE-2026-40372
Ubuntu26.04:LTSdotnet1010.0.107-10.0.7-0ubuntu1~26.04.1UBUNTU-CVE-2026-40372
Alpinev3.23, v3.24dotnet10-runtime10.0.7-r0ALPINE-CVE-2026-40372

From the distributions' data via OSV.dev: Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; the Alpine secdb, CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Ubuntu · Alpine.

Red Hat

Red Hat rates this Critical.

Red Hat's statement

No Red Hat products are affected as this vulnerability is specific to Microsoft.AspNetCore.DataProtection 10.0.6 from NuGet.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10dotnet10.0Not affected
Red Hat Enterprise Linux 8dotnet10.0Not affected
Red Hat Enterprise Linux 9dotnet10.0Not affected
Red Hat Hardened Imagesdotnet10.0Not affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-40372.

Attack patterns (CAPEC)

  • CAPEC-463 Padding Oracle Crypto Attack Severity: High
  • CAPEC-475 Signature Spoofing by Improper Validation Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON