Skip to content
Fencer Intel
high 7.5

CVE-2026-109468 json

ASP.NET Core Denial of Service Vulnerability

published 25d ago modified 9d ago also EUVD-2026-102468

cvss
7.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.0%
EPSS 1.0% chance of exploitation in 30 days, percentile 61%
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 Microsoft Visual Studio 2022 version 17.14 17.14.42
  • Microsoft Microsoft Visual Studio 2026 version 18.10 18.10.4
  • Microsoft System.Formats.Cbor 10.0.13

Is CVE-2026-109468 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 Fencer

Vendor 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-109468 updated cvss 7.5

dotnet: ASP.NET Core: Denial of Service via unthrottled resource allocation

  • Red Hat Hardened Images dotnet8.0 8.0.131-0.1.hum1
    not 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
no
Technical impact
partial
Assessed
25d ago

Exploit prediction

0.95% chance of exploitation in the next 30 days, higher than 61% 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 Microsoft Visual Studio 2022 version 17.14
  • Microsoft Microsoft Visual Studio 2026 version 18.10
  • Microsoft System.Formats.Cbor

Classification

Weakness
  • CWE-770 Allocation of Resources Without Limits or Throttling

References

Sources

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.