CVE-2026-40372

CRITICALPre-NVD 9.19.1
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.1 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 11.2%, top 5% 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).

Triggered by: NVD CVSS baseline
Sources: cna:microsoft, epss
Trending — 3 sources updated this weekElevated
9.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 11%CVSS: 9.1Exploit: NoneExposed: 0

A fix is available — apply it.

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

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 computed
Severity91% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
95.5%
KEV
Not listed

Published

April 21, 2026

Last Modified

July 15, 2026

Advisory Details (1)

Auto-updated Apr 28, 2026
Patch available. Sources: microsoft.
microsoft Patch Available

Security 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-40372

Vendor 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 / EcosystemFixed in / PatchReleasedSource
ubuntudotnet10 (10.0.107-10.0.7-0ubuntu1~25.10.1) @ questing2026-06-15ubuntu
ubuntudotnet10 (10.0.107-10.0.7-0ubuntu1~26.04.1) @ resolute2026-06-15ubuntu

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)
PackageVulnerable rangeFixed inDependents
Microsoft.AspNetCore.DataProtection10.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 10× in last 7d / 34× 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 134 total refreshes for this CVE.

  1. 2026-07-23 14:18 UTCEPSS rescore
  2. 2026-07-23 14:18 UTCEPSS rescore
  3. 2026-07-23 03:11 UTCEG score recompute
  4. 2026-07-22 14:08 UTCEPSS rescore
  5. 2026-07-21 15:24 UTCEPSS rescore
  6. 2026-07-20 17:32 UTCOSV refresh
  7. 2026-07-20 17:08 UTCEPSS rescore
  8. 2026-07-19 14:31 UTCEPSS rescore
  9. 2026-07-19 02:29 UTCEPSS rescore
  10. 2026-07-18 10:04 UTCEPSS rescore
  11. 2026-07-16 17:03 UTCEPSS rescore
  12. 2026-07-15 16:57 UTCEPSS rescore
  13. 2026-07-15 16:57 UTCEPSS rescore
  14. 2026-07-15 02:00 UTCEPSS rescore
  15. 2026-07-13 22:30 UTCEPSS rescore
  16. 2026-07-12 05:46 UTCEPSS rescore
  17. 2026-07-11 08:27 UTCEPSS rescore
  18. 2026-07-09 19:10 UTCEPSS rescore
  19. 2026-07-08 15:15 UTCEPSS rescore
  20. 2026-07-07 13:46 UTCEPSS rescore
  21. 2026-07-06 16:27 UTCEPSS rescore
  22. 2026-07-06 16:27 UTCEPSS rescore
  23. 2026-07-06 02:23 UTCEPSS rescore
  24. 2026-07-06 02:23 UTCEPSS rescore
  25. 2026-07-05 02:30 UTCEPSS rescore
Show 75 more
  1. 2026-07-01 15:06 UTCEPSS rescore
  2. 2026-06-30 23:22 UTCEPSS rescore
  3. 2026-06-29 14:06 UTCEPSS rescore
  4. 2026-06-28 04:56 UTCEPSS rescore
  5. 2026-06-27 03:08 UTCEPSS rescore
  6. 2026-06-25 13:49 UTCEPSS rescore
  7. 2026-06-25 13:49 UTCEPSS rescore
  8. 2026-06-24 14:05 UTCEPSS rescore
  9. 2026-06-23 21:33 UTCEPSS rescore
  10. 2026-06-22 14:25 UTCEPSS rescore
  11. 2026-06-22 14:25 UTCEPSS rescore
  12. 2026-06-21 14:56 UTCEPSS rescore
  13. 2026-06-21 14:56 UTCEPSS rescore
  14. 2026-06-21 01:59 UTCEPSS rescore
  15. 2026-06-19 19:25 UTCEPSS rescore
  16. 2026-06-18 17:52 UTCEPSS rescore
  17. 2026-06-18 17:52 UTCEPSS rescore
  18. 2026-06-17 17:53 UTCEPSS rescore
  19. 2026-06-16 17:52 UTCEPSS rescore
  20. 2026-06-15 17:49 UTCEPSS rescore
  21. 2026-06-15 03:02 UTCVendor advisory
  22. 2026-06-14 22:01 UTCVendor advisory
  23. 2026-06-14 17:46 UTCVendor advisory
  24. 2026-06-13 23:00 UTCEPSS rescore
  25. 2026-06-12 23:12 UTCEPSS rescore
  26. 2026-06-12 23:12 UTCEPSS rescore
  27. 2026-06-12 06:25 UTCVendor advisory
  28. 2026-06-12 02:12 UTCVendor advisory
  29. 2026-06-11 21:58 UTCVendor advisory
  30. 2026-06-11 17:43 UTCVendor advisory
  31. 2026-06-11 14:00 UTCEPSS rescore
  32. 2026-06-10 22:18 UTCEPSS rescore
  33. 2026-06-10 21:22 UTCVendor advisory
  34. 2026-06-10 17:09 UTCVendor advisory
  35. 2026-06-10 13:22 UTCEPSS rescore
  36. 2026-06-10 13:22 UTCEPSS rescore
  37. 2026-06-10 12:50 UTCVendor advisory
  38. 2026-06-10 08:36 UTCVendor advisory
  39. 2026-06-10 04:23 UTCVendor advisory
  40. 2026-06-10 00:09 UTCVendor advisory
  41. 2026-06-09 18:17 UTCVendor advisory
  42. 2026-06-09 14:04 UTCVendor advisory
  43. 2026-06-09 09:50 UTCVendor advisory
  44. 2026-06-09 04:22 UTCVendor advisory
  45. 2026-06-08 14:17 UTCEPSS rescore
  46. 2026-06-08 14:17 UTCEPSS rescore
  47. 2026-06-08 11:39 UTCVendor advisory
  48. 2026-06-08 07:21 UTCVendor advisory
  49. 2026-06-08 03:08 UTCVendor advisory
  50. 2026-06-07 22:54 UTCVendor advisory
  51. 2026-06-07 18:40 UTCVendor advisory
  52. 2026-06-07 15:25 UTCEPSS rescore
  53. 2026-06-07 15:25 UTCEPSS rescore
  54. 2026-06-07 14:18 UTCVendor advisory
  55. 2026-06-07 10:04 UTCVendor advisory
  56. 2026-06-07 05:50 UTCVendor advisory
  57. 2026-06-07 01:35 UTCVendor advisory
  58. 2026-06-06 13:47 UTCEPSS rescore
  59. 2026-06-06 13:47 UTCEPSS rescore
  60. 2026-06-06 11:01 UTCVendor advisory
  61. 2026-06-06 06:00 UTCVendor advisory
  62. 2026-06-06 00:54 UTCVendor advisory
  63. 2026-06-05 22:47 UTCEPSS rescore
  64. 2026-06-05 20:41 UTCVendor advisory
  65. 2026-06-05 11:14 UTCVendor advisory
  66. 2026-06-05 06:30 UTCVendor advisory
  67. 2026-06-05 06:10 UTCEPSS rescore
  68. 2026-06-05 06:10 UTCEPSS rescore
  69. 2026-06-04 19:12 UTCVendor advisory
  70. 2026-06-04 14:57 UTCVendor advisory
  71. 2026-06-04 13:12 UTCEPSS rescore
  72. 2026-06-04 13:12 UTCEPSS rescore
  73. 2026-06-03 22:40 UTCVendor advisory
  74. 2026-06-03 18:09 UTCVendor advisory
  75. 2026-06-03 13:55 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-40372?
CVE-2026-40372 is a critical vulnerability published on April 21, 2026. Improper verification of cryptographic signature in ASP.NET Core allows an unauthorized attacker to elevate privileges over a network.
When was CVE-2026-40372 disclosed?
CVE-2026-40372 was first published in the National Vulnerability Database on April 21, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-40372 actively exploited?
CVE-2026-40372 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 95.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-40372?
CVE-2026-40372 has a CVSS v4.0 base score of 9.1 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-40372?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-40372, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-40372

Explore →

Is Your Infrastructure Affected by CVE-2026-40372?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.