
Microsoft revised CVE-2026-102204 on October 20 to say the Important-rated local privilege-escalation flaw is in Windows Subsystem for Linux 2—not Microsoft Defender for Endpoint for Linux, as the original October 13 record indicated. [1] [11] Microsoft now lists WSL 3.0.1 as the fixed build and recommends that WSL users install the latest version. [1]
What Microsoft changed
Microsoft’s machine-readable Security Update Guide now titles CVE-2026-102204 “Windows Subsystem for Linux Elevation of Privilege Vulnerability,” maps the affected product to “Windows Subsystem for Linux (WSL2),” and marks customer action as required. [1] The October 20 revision note says Microsoft updated the CVE to reflect that the vulnerability is in WSL and recommends installing the latest version. [1]
The same record describes improper link resolution before file access, says a successful attacker could gain SYSTEM privileges, assigns a CVSS 3.1 base score of 7.8, and rates the issue Important. [1] Microsoft’s exploit-status fields say the issue was not publicly disclosed, was not known to be exploited, and was assessed as less likely to be exploited at the reporting cutoff. [1]
Why the correction matters
On October 13, the record was associated with Microsoft Defender for Endpoint for Linux. [11] The October 20 successor record instead identifies WSL 2 and a WSL fixed build. [1] That changes which administrators should inventory and which update path applies. [1] [11] Earlier summaries that copied the original product label may now be stale. [1] [11]
Who is affected—and who is not
Phone readers: swipe the table left to see every column.
| Environment | MSRC scope | Practical action |
|---|---|---|
| Windows device running WSL 2 with WSL older than 3.0.1 | Based on Microsoft’s fixed-build field, it is below the listed fixed floor. [1] | Update WSL, then verify the reported package version. [2] |
| Windows device running WSL 2 version 3.0.1 or later | At or above Microsoft’s listed fixed build. [1] | Record the version and keep normal WSL updates enabled. [2] Microsoft still recommends the latest version. [1] |
| Windows device with no WSL installed | Not the product named in this advisory. [1] | No CVE-specific action beyond normal Windows patching. [1] |
| WSL 1 distribution | Microsoft’s affected-product field specifically names WSL 2. [1] | Do not assume the distro-mode display proves the WSL package itself is current; inventory the package with wsl --version. [2] |
| Microsoft Defender for Endpoint for Linux without WSL | The October 13 snapshot named that product, but the October 20 MSRC successor no longer identifies it as the affected product for this CVE. [11] [1] | Do not use the corrected WSL advisory as evidence that Defender for Endpoint for Linux remains affected. [11] [1] |
| Mac | Not affected by this WSL advisory. [1] | No same-day production macOS security update was listed in Apple’s checked public sources. [6] [7] |
How to check and update WSL safely
- Open PowerShell or Windows Terminal.
- Check the installed WSL package version. Microsoft documents
wsl --versionfor component version information. [2]
Look for a WSL version of 3.0.1 or later. Microsoft’s CVE record lists 3.0.1 as the fixed build. [1]wsl --version - Inventory distributions and their WSL mode. Microsoft documents
wsl --list --verboseto show installed distributions, state, and whether each uses WSL 1 or WSL 2. [2]wsl --list --verbose - Install the current stable WSL update. Microsoft documents
wsl --updateas the command to update WSL to the latest version. [2]
Do not addwsl --update--pre-releasefor ordinary remediation; Microsoft documents that switch for preview WSL builds. [3] - Restart WSL workloads at a controlled time. Practical guidance: save work, stop development servers and containers cleanly, then restart the affected WSL environment so updated components are in use. [2] This is risk-based operational advice, not a claim that every update requires a Windows reboot.
- Verify again. Run
wsl --versionafter the update and record the result. [2] Practical guidance for a business fleet: sample representative developer, container, and automation systems before broad deployment. [2]
What remains unknown
No public exploit is listed
Microsoft’s current record says the flaw was not publicly disclosed and was not known to be exploited at the reporting cutoff. [1] That is a point-in-time vendor status, not a guarantee that exploitation cannot occur. [1]
Microsoft does not describe a remote attack
The CVSS vector is local, requires low privileges, and requires no user interaction. [1] The article therefore does not characterize the issue as an internet-wide remote-code-execution event. [1]
The fixed build is clear
MSRC lists WSL 3.0.1 as the fixed build and links to Microsoft’s WSL 3.0.1 release. [1] At the cutoff, Microsoft’s WSL release page labeled 3.0.3 as the latest stable release and 3.0.4 as a pre-release. [4] The normal update command targets the latest version, while Microsoft documents a separate --pre-release switch for previews. [2] [3]
Home and business actions
Home users and developers
Business and managed fleets
- Inventory WSL package versions separately from Windows OS builds and Linux distribution versions. [1] [2]
- Prioritize shared developer workstations, build systems, and other machines where lower-privileged users can run local code. [1]
- Practical guidance: pilot the stable WSL update against container, VPN, endpoint-security, file-mount, and development workflows before broad rollout. [2]
- Retain the before/after version and exception owner for systems that cannot update promptly. [1] [2]
Good and bad points
Good
Bad
- The original October 13 product label could leave WSL administrators looking in the wrong place. [1] [11]
- A local low-privilege attacker could potentially reach SYSTEM privileges, according to Microsoft’s record. [1]
- Organizations must track the WSL application package independently of the Windows cumulative-update level and each distribution’s WSL 1/2 mode. [1] [2]
macOS check: no same-day production release
At the reporting cutoff, Apple’s security-release table still listed macOS Golden Gate 27.0.1, macOS Tahoe 26.7.1, and macOS Sequoia 15.8.1 from September 28 as the newest production macOS entries. [6] Apple’s Background Security Improvements page still listed the March 17 WebKit release as its newest dated entry. [7] Apple’s developer feed listed macOS 27.2 RC on October 19; a release candidate is not a same-day public production security release. [8]
FAQ
Is this a new Windows patch released on October 20?
No. Microsoft originally published CVE-2026-102204 on October 13 and revised the product scope on October 20. [1] The current Windows 11 production security baseline remains the October 13 cumulative update. [5]
What WSL version fixes CVE-2026-102204?
Microsoft’s current CVRF record lists WSL 3.0.1 as the fixed build. [1] A later stable WSL version is also above that minimum; use Microsoft’s normal wsl --update path rather than selecting an older package manually. [2]
Does Windows Update alone prove WSL is fixed?
Not necessarily. Microsoft documents WSL as an independently updatable package and provides wsl --version and wsl --update. [2] Verify the WSL version directly instead of inferring it only from the Windows OS build. [2]
Official sources and related reading
- Microsoft Security Response Center — October 2026 CVRF, including CVE-2026-102204 revision 2.0
- Microsoft Learn — Basic commands for WSL
- Microsoft Learn — Install WSL and preview-update distinction
- Microsoft WSL repository — Releases
- Microsoft — Windows 11 release information
- Apple — Security releases
- Apple — Background Security Improvements by date
- Apple Developer — Software releases
- The IT Guys — Microsoft October 2026 Patch Tuesday guide
- The IT Guys media provenance note — original AI-generated editorial artwork; generation, transformation, and exact-file review receipts are retained privately.
- CIRCL Vulnerability-Lookup — preserved pre-correction CVE record showing Microsoft Defender for Endpoint for Linux
Reporting cutoff: October 20, 2026 at 7:32 p.m. EDT (23:32 UTC). This article distinguishes Microsoft’s same-day CVE scope correction from the October 13 Patch Tuesday release and from Apple’s October 19 developer release candidates. [1] [5] [8] The featured image is an original AI-generated editorial illustration and does not depict a real interface, device alert, or attack. [10]
