Home › Vulnerabilities

Docker Desktop for Windows (WSL2 backend) Flaw CVE-2026-112917: Update Now

Published November 3, 2026 · Last updated November 3, 2026

Windows Docker CVE Critical Patch

The short version: CVE-2026-112917 is a critical-severity security flaw in Docker Desktop for Windows (WSL2 backend). The National Vulnerability Database (NVD) published it on November 3, 2026, and the score it lists is 9.2 out of 10. When FraudMeNot checked on November 3, 2026, CISA had not added CVE-2026-112917 to its Known Exploited Vulnerabilities catalog, so there was no public U.S. government confirmation of attacks yet. A fix is available, which is why this page focuses on who should update and how.

What the official record says about CVE-2026-112917

The record was filed by docker.com. In its own words: "In Docker Desktop for Windows with the WSL2 backend, an unprivileged Linux container can use 32-bit socketcall to bypass the default seccomp restriction on AF_VSOCK. This can expose host-facing services and Windows files accessible to the logged-in user. The issue affects x86-64 WSL2; LinuxKit-based backends are unaffected. The issue is fully fixed only with Docker Desktop 4.98.0 or later and WSL 3.0.3 or later. Docker Desktop 4.98.0 or later running on an older WSL remains affected."

Why Docker Desktop for Windows (WSL2 backend) admins should care

Severity scores use the Common Vulnerability Scoring System (CVSS). the address listed on docker.com rated CVE-2026-112917 9.2 (Critical) under CVSS 4.0. Reading that rating in everyday terms: it can be reached only with local access to the system; an attacker needs a low-privilege account; no one has to click or open anything. If it is abused, the rated damage to keeping data private is high, to keeping data unaltered is high, and to keeping Docker Desktop for Windows (WSL2 backend) running is none. Scoring string: CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X.

The type of bug behind CVE-2026-112917

NVD classifies it using MITRE's Common Weakness Enumeration:

  • CWE-424, Improper Protection of Alternate Path. MITRE describes this class of bug as follows: "The product does not sufficiently protect all possible paths that a user can take to access restricted functionality or resources."

Vendor remediation for CVE-2026-112917

The vendor advisory remediation for operators of Docker Desktop for Windows (WSL2 backend), quoted for this page, is: "Update Docker Desktop for Windows to version 4.98.0 or later, and update WSL to version 3.0.3 or later (run wsl --update, or install the WSL 3.0.3 release from Microsoft). Both are needed: Docker Desktop 4.98.0 or later running on an older WSL is still affected. Docker's release notes for 4.98.0 list the fix. The LinuxKit-based backends are not affected. Until you can update, avoid running untrusted or unreviewed containers on the WSL2 backend, and do not pull images from sources you do not trust."

What to do about it

  • Update now: Update Docker Desktop for Windows to version 4.98.0 or later, and update WSL to version 3.0.3 or later (run wsl --update, or install the WSL 3.0.3 release from Microsoft). Both are needed: Docker Desktop 4.98.0 or later running on an older WSL is still affected. Docker's release notes for 4.98.0 list the fix. The LinuxKit-based backends are not affected. Until you can update, avoid running untrusted or unreviewed containers on the WSL2 backend, and do not pull images from sources you do not trust.
  • Who should act: IT teams, managed service providers, and developers who run or ship Docker Desktop for Windows (WSL2 backend). Check every place it runs, including servers, build systems, containers, and older machines nobody watches closely.
  • Read the official advisory from Docker (linked under Sources) for exact fixed builds and any temporary workaround if you cannot patch today.
  • After patching, confirm the new version is actually running and review logs from November 3, 2026 onward for anything unusual.
  • Home users: you do not need to buy or download anything because of CVE-2026-112917. A caller, text, or pop-up claiming your computer is "infected" with this CVE and asking for money or remote access is a scam.

CVE-2026-112917 record details from CISA and NVD

  • Attack complexity for CVE-2026-112917: low
  • CVE-2026-112917 attack requirements: none
  • Impact on connected systems: secrecy high, integrity high, availability none.
  • Who mapped the weakness type: the address listed on docker.com (Secondary)
  • References in the NVD record: 3.

Dates to know

  • November 3, 2026: NVD publishes CVE-2026-112917.
  • November 3, 2026: FraudMeNot checks the CISA KEV catalog; CVE-2026-112917 is not listed.
  • November 3, 2026: most recent NVD update (record status: Received).

Official references

Links listed in the NVD record (labels in brackets come from NVD):

Sources

General education only, not security advice. Facts checked against the sources above on the date shown.