Windows BITS EUVD-2026-100094

Exploitation requires the attacker to already have authenticated local access with at least low-level privileges on the target (CVSS PR:L, AV:L) - there is no remote or network vector and no user interaction is needed (UI:N). The flaw resides in the Windows Background Intelligent Transfer Service (BITS), a default-enabled component present on all supported Windows client and server editions, so no non-default configuration is required to reach the vulnerable service. The primary limiting factor is the need for a pre-existing local foothold; this is a privilege-escalation primitive used after initial access, not an initial-access vulnerability. Servers and workstations where untrusted users can run code (multi-user, RDP, or kiosk hosts) face the highest realistic exposure.

This is a credible but not emergency-level priority. The CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:N) confirms a local privilege-escalation flaw requiring the attacker to already hold valid low-level credentials on the host - it is not remotely exploitable, which caps its urgency relative to network-facing CVEs. CISA's SSVC framework aligns with this: Exploitation=none (no observed or public exploitation), Automatable=no (cannot be reliably mass-scripted across targets), but Technical Impact=total, consistent with the C:H/I:H/A:H impact and the fact that successful exploitation typically yields SYSTEM-level control. There is no CISA KEV listing and no POC in the provided data, so exploitation status is 'no public exploit identified at time of analysis.' No EPSS score was supplied, so probabilistic exploitation likelihood cannot be quantified from this input. The signals are internally consistent (local EoP, no known exploitation, high impact) with no contradictions to flag. Bottom line: a real priority for privileged endpoints and multi-user servers because it completes a local-attacker-to-SYSTEM chain, but it is a second-stage vulnerability - an attacker needs an initial foothold first - so it should be patched on the normal-to-expedited Patch Tuesday cycle rather than treated as a drop-everything remote threat.

An attacker who has already gained low-privileged code execution on a Windows host (e.g., via phishing or a compromised standard user account) invokes the Background Intelligent Transfer Service and supplies crafted input that triggers an integer overflow leading to a heap buffer overflow. The corrupted heap allocation is leveraged to execute attacker-controlled code in the context of the privileged BITS service, elevating from standard user to SYSTEM. No public exploit code is identified in the available data, so this scenario is inferred from the CWE-122 heap-overflow mechanism and the AV:L/PR:L vector.