Improper verification of cryptographic signature in ASP.NET Core allows an unauthorized attacker to elevate privileges over a network.
CVE-2026-40372
This critical-severity CVE scores 9.1 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 11.2%, top 4% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 9.1
- EG Score
- 9.1(medium)
- EG Risk
- 72(Track)EG Risk 72/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity91% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 11%
- EPSS %ILE
- 96%
- KEV
- Not listed
Published
April 21, 2026
Last Modified
August 14, 2026
Advisory Details (1)
Auto-updated Sep 16, 2026Security Update Guide - Microsoft Security Response Center
Security Update Guide - Microsoft Security Response Center. Patch available via Microsoft Security Update
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-40372Vendor Advisories for CVE-2026-40372(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(2)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| ubuntu | dotnet10 (10.0.107-10.0.7-0ubuntu1~25.10.1) @ questing | 2026-06-15 | ubuntu |
| ubuntu | dotnet10 (10.0.107-10.0.7-0ubuntu1~26.04.1) @ resolute | 2026-06-15 | ubuntu |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(1 across 1 ecosystem)
NuGet(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| Microsoft.AspNetCore.DataProtection | 10.0.0 ... 10.0.6 (7 versions) | 10.0.7 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Additional Vendor Advisories
(2)
Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.
Data Freshness Timeline
(refreshed 6× in last 7d / 27× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 242 total refreshes for this CVE.
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-17 19:30 UTCEPSS rescore
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-15 03:11 UTCEPSS rescore
- 2026-09-12 15:01 UTCEPSS rescore
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 09:37 UTCEPSS rescore
- 2026-09-10 09:34 UTCEPSS rescore
- 2026-09-08 22:00 UTCEPSS rescore
- 2026-09-07 16:01 UTCEPSS rescore
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-04 05:06 UTCEPSS rescore
- 2026-09-02 15:08 UTCOSV refresh
- 2026-09-02 14:12 UTCEPSS rescore
- 2026-09-01 13:53 UTCEPSS rescore
- 2026-09-01 04:39 UTCEPSS rescore
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-28 21:41 UTCEPSS rescore
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-23 00:19 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 10:30 UTCVendor advisory
- 2026-08-16 06:17 UTCEG score recompute
- 2026-08-16 06:17 UTCVendor advisory
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-15 01:16 UTCVendor advisory
- 2026-08-14 21:03 UTCVendor advisory
- 2026-08-14 16:49 UTCVendor advisory
- 2026-08-14 12:55 UTCVendor advisory
- 2026-08-14 08:41 UTCVendor advisory
- 2026-08-14 04:28 UTCEG score recompute
- 2026-08-14 04:28 UTCVendor advisory
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 08:43 UTCVendor advisory
- 2026-08-13 03:06 UTCVendor advisory
- 2026-08-12 22:53 UTCVendor advisory
- 2026-08-12 18:39 UTCEG score recompute
- 2026-08-12 18:39 UTCVendor advisory
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-12 01:19 UTCVendor advisory
- 2026-08-11 21:06 UTCVendor advisory
- 2026-08-11 16:51 UTCEG score recompute
- 2026-08-11 16:51 UTCVendor advisory
- 2026-08-11 13:43 UTCEPSS rescore
- 2026-08-11 06:38 UTCVendor advisory
- 2026-08-11 02:25 UTCEG score recompute
- 2026-08-11 02:25 UTCVendor advisory
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 09:49 UTCVendor advisory
- 2026-08-10 05:36 UTCVendor advisory
- 2026-08-10 01:23 UTCVendor advisory
- 2026-08-09 21:09 UTCVendor advisory
- 2026-08-09 16:56 UTCEG score recompute
- 2026-08-09 16:56 UTCVendor advisory
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 12:43 UTCVendor advisory
- 2026-08-09 07:54 UTCVendor advisory
- 2026-08-09 03:40 UTCEG score recompute
- 2026-08-09 03:40 UTCVendor advisory
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 10:02 UTCVendor advisory
- 2026-08-08 05:49 UTCVendor advisory
- 2026-08-08 01:36 UTCVendor advisory
- 2026-08-07 21:23 UTCVendor advisory
- 2026-08-07 17:10 UTCEG score recompute
- 2026-08-07 17:10 UTCVendor advisory
- 2026-08-07 12:56 UTCVendor advisory
- 2026-08-06 21:49 UTCVendor advisory
- 2026-08-06 17:26 UTCEG score recompute
- 2026-08-06 17:26 UTCVendor advisory
- 2026-08-06 13:46 UTCEPSS rescore
- 2026-08-06 11:55 UTCVendor advisory
- 2026-08-06 07:37 UTCVendor advisory
- 2026-08-06 03:23 UTCVendor advisory
- 2026-08-05 23:10 UTCEG score recompute
- 2026-08-05 23:10 UTCVendor advisory
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-04 10:38 UTCEPSS rescore
- 2026-08-04 05:50 UTCVendor advisory
- 2026-08-04 01:36 UTCVendor advisory
- 2026-08-03 21:22 UTCVendor advisory
- 2026-08-03 01:25 UTCVendor advisory
- 2026-08-02 21:11 UTCVendor advisory
- 2026-08-02 16:58 UTCVendor advisory
- 2026-08-02 12:44 UTCEG score recompute
- 2026-08-02 12:44 UTCVendor advisory
- 2026-08-02 02:27 UTCEPSS rescore
- 2026-08-01 04:16 UTCEPSS rescore
Related CVEs(same vendor + same CWE)
Same vendor
10 shownubuntu
- CVE-2004-0989EG 10.0EPSS p98HIGH
- CVE-2004-0990EG 10.0EPSS p98HIGH
- CVE-2004-1010EG 10.0EPSS p95HIGH
- CVE-2004-0941EG 10.0EPSS p96HIGH
- CVE-2004-0981EG 10.0EPSS p93HIGH
- CVE-2004-0882EG 10.0EPSS p96HIGH
- CVE-2004-0888EG 10.0EPSS p95HIGH
- CVE-2004-1012EG 10.0EPSS p93HIGH
- CVE-2004-1013EG 10.0EPSS p93HIGH
- CVE-2004-1018EG 10.0EPSS p97HIGH
Same CWE
10 shownCWE-347
Frequently asked(5)
What is CVE-2026-40372?
When was CVE-2026-40372 disclosed?
Is CVE-2026-40372 actively exploited?
What is the CVSS score of CVE-2026-40372?
How do I remediate CVE-2026-40372?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-40372
Is Your Infrastructure Affected by CVE-2026-40372?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.