Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach QUIC/HTTP3 endpoint over network
-
ExploitWin race on insecurely initialized default
-
ExecutionBypass intended security feature
-
ImpactDisrupt service availability across scope
Vulnerability Assessment
| Weakness |
CWE
|
| Exploitation Conditions | Exploitation requires the target to be running Microsoft QUIC (MsQuic) with QUIC/HTTP3 or SMB-over-QUIC actually enabled and network-reachable - this is not a universal default across all Windows roles, which materially narrows the exposed attack surface. The CVSS AC:H further indicates a non-deterministic prerequisite (a timing/race window or a specific transient state produced by the insecure default variable initialization) that the attacker cannot directly control, limiting reliability. No authentication is required (PR:N) and no user interaction is needed (UI:N), but the dependence on an enabled QUIC listener plus the race condition are the key limiting factors for defenders. Confirm the precise affected feature and configuration via the MSRC advisory. |
| Impact | This is a moderate-severity (CVSS 7.5) network-reachable issue whose real-world priority is tempered by several signals. The CVSS vector (AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:H) shows an unauthenticated, remotely reachable flaw, but the HIGH attack complexity (AC:H) means exploitation depends on conditions outside the attacker's control (likely a timing/race window or a specific non-default state arising from the insecure default variable initialization, CWE-453). Impact is skewed toward availability (A:H) with only limited integrity impact (I:L) and NO confidentiality impact (C:N), so despite the 'Authentication Bypass' tag this behaves as a security-feature-bypass/DoS-class issue rather than a data-disclosure or full-compromise bug. No EPSS score, no CISA KEV listing, and no public POC were provided, so there is no evidence of active or at-scale exploitation at time of analysis. Net: real but not an emergency - patch on a normal cadence for QUIC/HTTP3-exposed Windows hosts; the AC:H and availability-only impact argue against treating it as a drop-everything item. Note a tension to verify: the 'Authentication Bypass' tag conflicts with C:N/I:L (a true auth bypass would usually carry confidentiality or higher integrity impact) - treat the tag with caution and rely on the MSRC advisory for the precise security feature affected. |
| Exploit ScenarioDerived | A remote, unauthenticated attacker repeatedly connects to a Windows host exposing QUIC/HTTP3 (or SMB over QUIC) and exploits a security feature that is left in an insecure state due to default variable initialization. Because attack complexity is high, the attacker must win a specific timing or state condition to bypass the control, most plausibly degrading or disrupting the service (A:H). No public exploit code was identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 13, 2026
Microsoft QUIC (MsQuic) can be made to bypass a security feature over the network because a security-relevant variable is initialized to an insecure default (CWE-453), producing a CVSS 7.5 condition with no confidentiality impact, limited integrity impact and full availability impact (AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:H). The issue is unauthenticated and requires no user interaction, but is only reachable on hosts that actually run a network-exposed QUIC listener - HTTP/3 or SMB over QUIC - and the high attack complexity reflects a timing/transient-state prerequisite the attacker cannot directly control. No public exploit identified at time of analysis, and the CVE is not listed in CISA KEV; the MSRC update guide is the authoritative source for affected builds and fixes.
RemediationAI
No exact fix version is specified in the supplied intelligence, so the authoritative patch and affected-build list is the Microsoft MSRC update guide for CVE-2026-103577 (https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-103577); check it and apply the vendor build as soon as it is published. Where patching cannot be completed immediately, shrink the attack surface by disabling QUIC transports that are not required: turn off HTTP/3 in IIS/HTTP.sys and in client browsers so traffic falls back to HTTP/2 over TCP (trade-off: added latency and loss of 0-RTT/connection-migration benefits), and disable SMB over QUIC on servers where remote file access over that transport is unnecessary, forcing clients back to VPN or conventional SMB (trade-off: loss of the NAT/firewall-friendly UDP 443 path for mobile clients). Complement this by restricting inbound UDP 443 and the SMB-over-QUIC listener at host firewalls and network edges so only known clients can reach the service, and monitor for anomalous QUIC handshake/connection behavior; these compensating controls reduce exposure and the race window but do not eliminate the insecure default, so patching remains the primary fix.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 8 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause class is CWE-453, Insecure Default Variable Initialization: a variable that gates a security decision - for example a validation or permission flag, or a connection-state value used during QUIC handshake/connection handling - is left at a permissive or uninitialized default and can be reached before the code assigns the intended secure value. In Microsoft's QUIC implementation (MsQuic), which backs HTTP/3 in Windows/IIS and SMB over QUIC, the observable outcome is a security-feature bypass rather than memory corruption, which matches the assessed vector's C:N/I:L/A:H profile where availability impact dominates and the scope change (S:C) signals impact crossing a security boundary. The AC:H rating aligns with the independent assessment's description of a non-deterministic timing/race window or transient state created by the insecure default, meaning the window exists only briefly and the attacker cannot deterministically force it. No CPE strings were supplied in the source data, so exact affected builds and platform scope should be confirmed against the MSRC advisory.
Know when the next one hits your stack
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:H
Network-reachable QUIC with no auth (AV:N/PR:N); AC:H for the race/transient default-state prerequisite; scope change and availability-dominant impact, no confidentiality (C:N).
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
2DescriptionCVE.org
Insecure default variable initialization in Microsoft QUIC allows an unauthorized attacker to bypass a security feature over a network.
Executive ViewAI
Microsoft QUIC (MsQuic) contains a security feature bypass that can cause full availability impact on systems running network-exposed QUIC listeners, such as HTTP/3 or SMB over QUIC. The vulnerability is unauthenticated but requires a high-complexity timing condition, and no public exploit identified at time of analysis. With no vendor-released patch identified at time of analysis, leadership should prioritize identifying and restricting unnecessary QUIC listeners to protect service availability.
Interim mitigations: disable or restrict network-exposed QUIC listeners (HTTP/3, SMB over QUIC) where not required; implement network segmentation and access controls to limit reachability; enable monitoring for anomalous QUIC traffic.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
EUVD-2026-100390
GHSA-74jh-9hhr-rxh5
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB