---
id: "CVE-2026-112917"
kind: "vulnerability"
aliases: ["CVE-2026-112917"]
title: "Docker Desktop on Windows: container escapes seccomp to reach host files"
severity: "critical"
cvss: 9.2
epss: null
exploited: false
status: "open"
category: "runtime"
products: [{"name": "Docker Desktop (WSL 2 backend, Windows, x86-64)", "fixed": ["4.98.0 with WSL 3.0.3"], "affected": "< 4.98.0, or any version running WSL < 3.0.3", "ecosystem": "vendor"}]
ecosystems: []
tags: ["containers", "docker-desktop", "runtime", "windows", "wsl2"]
not_affected_if: ["linuxkit-backend", "no-docker-desktop", "non-x86-64"]
published_at: "2026-11-03T19:17:53+00:00"
first_seen_at: "2026-11-03T19:44:51+00:00"
updated_at: "2026-11-03T19:46:41+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-112917", "first_seen_at": "2026-11-03T19:44:51+00:00"}, {"source": "analyst", "url": null, "first_seen_at": "2026-11-03T19:46:41+00:00"}]
---

# Docker Desktop on Windows: container escapes seccomp to reach host files

In Docker Desktop for Windows with the WSL2 backend, an unprivileged Linux container can use the 32-bit socketcall syscall to bypass the default seccomp block on AF_VSOCK sockets. An attacker in a container can reach host-facing services and Windows files readable by the logged-in user.

_Summary, check and fix written by a model from the sources; labelled as such._

## Affected

- vendor:Docker Desktop (WSL 2 backend, Windows, x86-64) affected < 4.98.0, or any version running WSL < 3.0.3 fixed 4.98.0 with WSL 3.0.3

## How to check

- Docker Desktop version: About panel or 'docker version'; need 4.98.0 or later.
- WSL version: 'wsl --version'; need 3.0.3 or later (kernel 6.18.54.1). Both must be met.
- Applies only to the WSL 2 backend on x86-64; LinuxKit-based backends are stated unaffected (NVD).
- Exposure needs code running inside a Linux container (CVSS AV:L, PR:L), e.g. untrusted images or CI jobs.

## Fix

Update Docker Desktop to 4.98.0 or later AND WSL to 3.0.3 or later (wsl --update). Docker's 4.98.0 release notes: the AF_VSOCK bypass fix 'requires WSL 3.0.3 or later'; 4.98.0 on an older WSL stays affected per the NVD description.

## Timeline

- 2026-11-03T19:44:51+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-112917
- 2026-11-03T19:46:41+00:00 analyst — Docker 4.98.0 release notes (primary) list CVE-2026-112917 fixed, needing WSL 3.0.3+. WSL 3.0.3 and kernel release notes do not name the CVE; they only ship kernel 6.18.54.1, so the link is Docker's statement. No PoC or exploitation found. Attacker prerequisite: ability to run a container (CVSS local, low privileges). No Docker security-announcements entry yet. Did not search X.

## Documents

- [advisory] Docker Desktop release notes 4.98.0 https://docs.docker.com/desktop/release-notes/
- [fix] Release notes: github.com https://github.com/microsoft/WSL/releases/tag/3.0.3
- [fix] Release notes: github.com https://github.com/microsoft/WSL2-Linux-Kernel/releases/tag/linux-msft-wsl-6.18.54.1

## From the sources

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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_