CVE-2024-26190

Microsoft QUIC Denial of Service Vulnerability

HIGH
7.5
CVSS Score
Published: March 12, 2024 at 04:57 PM UTC
Updated: June 17, 2026 at 07:17 AM UTC
10 products affected across 1 vendorWindows Server 2022Windows 11 23H2Windows 11 22H2

Using Microsoft Visual Studio 2022 version 17.9 by Microsoft?

Get instant alerts when new vulnerabilities affect Microsoft Visual Studio 2022 version 17.9 - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.5
Exploit prediction
EPSS 3%
SSVC
No known exploit

Description

Microsoft QUIC Denial of Service Vulnerability

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

7.0.0 ≤ v < 7.0.178.0 ≤ v < 8.0.38.0.0 ≤ v < 8.0.37.0.08.0
Affected range stops below 7.0.17, so it looks safe — our inference, not a vendor statement
Affected range stops below 8.0.3, so it looks safe — our inference, not a vendor statement
7.3 ≤ v < 7.3.127.3.0 ≤ v < 7.3.127.4 ≤ v < 7.4.27.4.0 ≤ v < 7.4.27.3.07.4.0
Affected range stops below 7.3.12, so it looks safe — our inference, not a vendor statement
Affected range stops below 7.4.2, so it looks safe — our inference, not a vendor statement
17.0 ≤ v < 17.9.317.6.0 ≤ v < 17.6.1317.8.0 ≤ v < 17.8.8
Affected range stops below 17.6.13, so it looks safe — our inference, not a vendor statement
Affected range stops below 17.8.8, so it looks safe — our inference, not a vendor statement
Affected range stops below 17.9.3, so it looks safe — our inference, not a vendor statement
17.0 ≤ v < 17.9.317.4.0 ≤ v < 17.4.1717.6.0 ≤ v < 17.6.1317.8.0 ≤ v < 17.8.817.9.0 ≤ v < 17.9.317.017.4.017.6.017.8.0
Affected range stops below 17.4.17, so it looks safe — our inference, not a vendor statement
Affected range stops below 17.6.13, so it looks safe — our inference, not a vendor statement
Affected range stops below 17.8.8, so it looks safe — our inference, not a vendor statement
Affected range stops below 17.9.3, so it looks safe — our inference, not a vendor statement
v < 10.0.22000.283610.0.22000.0 ≤ v < 10.0.22000.283610.0.22000.0
Affected range stops below 10.0.22000.2836, so it looks safe — our inference, not a vendor statement
v < 10.0.22621.329610.0.22621.0 ≤ v < 10.0.22621.329610.0.22621.0
Affected range stops below 10.0.22621.3296, so it looks safe — our inference, not a vendor statement
v < 10.0.22631.329610.0.22631.0 ≤ v < 10.0.22631.329610.0.22631.0
Affected range stops below 10.0.22631.3296, so it looks safe — our inference, not a vendor statement
v < 10.0.20348.234010.0.20348.0 ≤ v < 10.0.20348.234010.0.20348.0
Affected range stops below 10.0.20348.2340, so it looks safe — our inference, not a vendor statement
v < 10.0.25398.76310.0.25398.0 ≤ v < 10.0.25398.76310.0.25398.0
Affected range stops below 10.0.25398.763, so it looks safe — our inference, not a vendor statement
10.0.25398.0 ≤ v < 10.0.25398.763
Affected range stops below 10.0.25398.763, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

SSVC — Action Prioritization

SSVCNo known exploitAutomatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.5HIGHmicrosoft
Vector?

Quick Info

StatusANALYZED
CWE
CWE-400NVD-CWE-noinfo

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card