VYPR
High severityNVD Advisory· Published Jun 2, 2026

CVE-2026-8936

CVE-2026-8936

Description

A VM panic vulnerability in Docker Desktop's grpcfuse kernel module allows for denial of service via deeply nested directories.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

A VM panic vulnerability in Docker Desktop's grpcfuse kernel module allows for denial of service via deeply nested directories.

Vulnerability

A VM panic vulnerability exists in the grpcfuse kernel module within Docker Desktop. This issue is triggered when a container creates deeply nested directories on a bind-mounted host folder and subsequently causes a dentry invalidation event, leading to unbounded recursion. This affects versions prior to Docker Desktop 4.76.0.

Exploitation

An attacker with the ability to run containers on a Docker Desktop instance can exploit this vulnerability. The attacker needs to create a container that binds to a host folder and then programmatically create a very deep nesting of directories within that bind mount. This action, when combined with a dentry invalidation event, triggers the unbounded recursion.

Impact

Successful exploitation of this vulnerability results in a VM panic, causing a denial of service for the Docker Desktop environment. This effectively halts all container operations and requires a restart of the Docker Desktop application.

Mitigation

This vulnerability has been fixed in Docker Desktop version 4.76.0, released on June 1, 2026 [1]. Users are advised to update to this version or later to resolve the issue. No workarounds are available for older versions.

AI Insight generated on Jun 2, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

1

Patches

0

No patches discovered yet.

Vulnerability mechanics

No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.

References

1

News mentions

0

No linked articles in our index yet.