CVE-2026-45646 json
OData for ASP.NET and ASP.NET Core Denial of Service Vulnerability
published 3mo ago modified 8d ago also EUVD-2026-43795
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.2%
- EPSS 1.2% chance of exploitation in 30 days, percentile 67%
- public exploits
- 0
- none known
Summary
Allocation of resources without limits or throttling in ASP.NET Core allows an unauthorized attacker to deny service over a network.
Patch / fix
- Microsoft AspNet.OData 7.8.0
- Microsoft AspNetCore.OData 9.5.0[SX1]
Is CVE-2026-45646 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-45646 updated cvss 7.5
dotnet: ASP.NET Core: Denial of Service via uncontrolled resource allocation
-
Red Hat Hardened Images dotnet9.0 9.0.118-1.hum1, dotnet10.0 10.0.109-1.hum1, dotnet8.0 8.0.128-1.1.hum1not affected: component not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 3mo ago
Exploit prediction
1.17% chance of exploitation in the next 30 days, higher than 67% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/E:U/RL:O/RC:C |
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Microsoft AspNet.OData
- Microsoft AspNetCore.OData
Classification
- Weakness
-
- CWE-770 Allocation of Resources Without Limits or Throttling
References
-
msrc.microsoft.com
/update-guide/vulnerability/CVE-2026-45646
vendor-advisory, patch
Sources
- CVE List CVE-2026-45646
- NVD CVE-2026-45646
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.