CVE-2026-112917 in the critical feed json
Docker Desktop WSL2 AF_VSOCK isolation bypass via 32-bit socketcall
published 2026-11-03 5 d ago modified 2026-11-06 2 d ago also EUVD-2026-116144
- cvss
- 9.2
- version 4.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 8%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Docker Docker Desktop 4.98.0
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 4 d ago
Exploit prediction
0.18% chance of exploitation in the next 30 days, higher than 8% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 9.2 | 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 |
| CNA | 4.0 | 9.2 | 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 |
Affected products
- Docker Docker Desktop
Classification
- Weakness
-
- CWE-424 Improper Protection of Alternate Path
- Technology feeds
References
-
docs.docker.com
/desktop/release-notes/#4980
release-notes
-
github.com
/microsoft/WSL/releases/tag/3.0.3
release-notes
-
github.com
/microsoft/WSL2-Linux-Kernel/releases/tag/linux-msft-wsl-6.18.54.1
release-notes
Sources
- CVE List CVE-2026-112917
- NVD CVE-2026-112917
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.