Windows Container Isolation CVE-2026-70270

Requires the attacker to already hold valid low-privileged authenticated access on the local Windows host (PR:L, AV:L) and the ability to interact with the Windows Container Isolation FS Filter Driver (wcifs). Exploitation is inherently local - there is no network vector - and the driver is a standard component present on supported Windows client and server builds, so no special non-default configuration is indicated. Limiting factors: no remote exploitation, no exploitation without a pre-existing foothold, SSVC rates it non-automatable, and impact is confined to confidentiality (information disclosure) with no integrity or availability effect.

This is a moderate-severity, low-priority issue despite the 'elevate privileges' phrasing in the title. The CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N, base 5.5) describes a locally-exploitable flaw requiring existing low-level authentication, with impact limited to confidentiality (C:H) and NO integrity or availability impact - which is an information-disclosure profile, not a classic privilege-escalation one. Note the conflict: the title and CWE framing suggest EoP, but the impact metrics and the 'Information Disclosure' tag indicate the real outcome is memory/data disclosure via an untrusted pointer dereference (CWE-822), not code execution or integrity compromise - verify the actual impact with Microsoft's MSRC advisory. CISA's SSVC framework reinforces low urgency: Exploitation=none (no observed exploitation), Automatable=no (requires local access and cannot be reliably scripted at scale), though Technical Impact=total. No KEV listing and no public POC are indicated in the provided data, and no EPSS score was supplied. The local attack vector plus required pre-existing authentication substantially limits real-world risk: an attacker already needs a foothold on the host. This is a routine patch-cycle item, not an emergency.

An attacker who already has low-privileged authenticated access to a Windows host (for example, a standard local or domain user, or code running in a container context) invokes the Container Isolation FS Filter Driver in a way that triggers dereference of an attacker-influenced untrusted pointer, disclosing kernel or protected memory contents. No public exploit code is identified at time of analysis, and the local attack vector means remote-only attackers cannot trigger it directly.