CVE-2026-8936: 
Docker Desktop vulnerability analysis and mitigation

CVE-2026-8936 is a Denial of Service vulnerability in Docker Desktop caused by uncontrolled recursion (CWE-674) in the grpcfuse kernel module. When a container creates deeply nested directories on a bind-mounted host folder and triggers a dentry invalidation event, unbounded recursion occurs, causing a VM panic. The vulnerability affects Docker Desktop versions 4.33.0 through 4.76.0 (exclusive) and was published on June 2, 2026. It carries a CVSS v4.0 base score of 8.2 (High) (GitHub Advisory, Feedly).

The root cause is CWE-674 (Uncontrolled Recursion) in the grpcfuse kernel module used by Docker Desktop's virtual machine. When a container with a bind-mounted host folder creates a sufficiently deep directory hierarchy, a dentry (directory entry) invalidation event is triggered that causes the kernel module to recurse without bound, exhausting the stack and causing a VM panic. Exploitation requires local access and low-level privileges (the ability to create containers and mount host folders), with no user interaction or special attack conditions needed (GitHub Advisory, Feedly).

Successful exploitation causes a complete crash (panic) of the Docker Desktop virtual machine, resulting in a denial of service for all containers and workloads running within it. Both the vulnerable system and subsequent system availability are rated High, meaning the entire Docker Desktop environment becomes unavailable until restarted. There is no confidentiality or integrity impact — the vulnerability is purely an availability issue with no data exposure or unauthorized modification risk (GitHub Advisory, Feedly).

1. Gain container access: Obtain low-privileged local access to a Docker Desktop instance (version < 4.76.0) with permission to create containers and configure bind mounts.
2. Configure a bind mount: Launch a container with a host directory bind-mounted (e.g., docker run -v /host/path:/mnt/hostdir <image>).
3. Create deeply nested directories: Inside the container, programmatically create an extremely deep directory hierarchy on the bind-mounted path (e.g., using a script: mkdir -p /mnt/hostdir/a/b/c/.../z repeated to hundreds or thousands of levels).
4. Trigger dentry invalidation: Perform filesystem operations (e.g., renaming, deleting, or stat-ing directories) that cause the kernel to invalidate directory entry (dentry) cache entries for the nested structure.
5. Induce VM panic: The grpcfuse kernel module enters unbounded recursion while processing the dentry invalidation event, exhausting the kernel stack and causing a VM panic, crashing the entire Docker Desktop virtual machine (GitHub Advisory, Feedly).

• Logs: Docker Desktop VM crash logs or kernel panic traces referencing grpcfuse module stack overflow or recursion depth exceeded; unexpected VM restart events in Docker Desktop logs.
• Process/System: Sudden termination of the Docker Desktop LinuxKit VM process; all running containers becoming unresponsive simultaneously without user-initiated stop.
• File System: Presence of abnormally deep directory trees (hundreds or thousands of levels) within bind-mounted host folders accessible to containers.
• Network: Loss of connectivity to all Docker-managed container networks immediately following the creation of deeply nested directories inside a container with bind mounts.

Docker has released a fix in Docker Desktop 4.76.0, which resolves the unbounded recursion in the grpcfuse kernel module. Users should upgrade to version 4.76.0 or later as the primary remediation (GitHub Advisory, Docker Release Notes). As a temporary workaround until patching is possible, restrict container creation and bind-mount permissions to trusted users only, and consider monitoring or limiting directory depth within containers that use bind mounts.

The vulnerability received routine coverage from vulnerability aggregators and threat intelligence platforms shortly after disclosure, including mentions in Cyfirma's Weekly Intelligence Report for June 12, 2026 (Cyfirma). A Zero Day Initiative advisory (ZDI-26-327) was also published (ZDI). Social media activity was limited to automated CVE notification accounts on Bluesky and Nitter. No significant researcher commentary or widespread community discussion has been observed, consistent with the low EPSS score and absence of active exploitation.