high CVSS 7

CVE-2024-6222·Docker vulnerability

In Docker Desktop before v4.29.0, an attacker who has gained access to the Docker Desktop VM through a container breakout can further escape to the host by passing extensions and dashboard related IPC messages. Docker Desktop v4.29.0 https://docs.docker.com/desktop/release-notes/#4290 fixes the issue on MacOS, Linux and Windows with Hyper-V backend. As exploitation requires "Allow only extensions distributed through the Docker Marketplace" to be disabled, Docker Desktop v4.31.0 https://docs.docker.com/desktop/release-notes/#4310 additionally changes the default configuration to enable this setting by default.

Severity: high
Software: Docker
Fixed in: 4.29.0
Published: 2024-07-09

Affected versions

Until: 4.29.0

Fixed in: 4.29.0

How to fix this CVE

Update Docker Desktop to version 4.29.0 or later to patch the container-to-host escape vulnerability affecting the IPC message handling system. Additionally, upgrade to Docker Desktop v4.31.0 or newer to benefit from the hardened default configuration that restricts unsigned extensions, which reduces the attack surface for this vulnerability class.

sudo dnf upgrade docker-ce

Defensia detects this vulnerability

How to check if you are affected

Run 'docker --version' to confirm your current Docker version and compare against 4.29.0
Check 'docker info' output and verify the Server Version field; if below 4.29.0, the system is vulnerable
Inspect Docker daemon logs at '/var/lib/docker/containers/*/json.log' for unusual IPC communication patterns or extension-related errors
After patching, re-run 'docker --version' and confirm the version is 4.29.0 or higher; then restart Docker daemon with 'sudo systemctl restart docker'

FAQ

What is CVE-2024-6222?

CVE-2024-6222 is a privilege escalation vulnerability in Docker Desktop that allows an attacker who has already escaped from a container to further break out to the host system by exploiting improper validation of IPC (inter-process communication) messages used by Docker extensions and the dashboard.

Is CVE-2024-6222 being actively exploited?

No, CVE-2024-6222 is not currently listed on CISA's Known Exploited Vulnerabilities catalog, and no public exploits are available. However, the vulnerability requires significant pre-existing access (container breakout), so real-world exploitation risk depends on your container security posture.

What versions of Docker are affected by CVE-2024-6222?

All versions of Docker Desktop prior to 4.29.0 are vulnerable, regardless of operating system (macOS, Linux, Windows with Hyper-V backend).

How do I check if my server is vulnerable to CVE-2024-6222?

Run 'docker --version' and check if the reported version is below 4.29.0. On Docker Desktop, also verify that 'Allow only extensions distributed through the Docker Marketplace' is enabled in Settings > Extensions to confirm the default hardening is active.

Does Defensia detect CVE-2024-6222?

Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Docker is installed on a monitored server, CVE-2024-6222 will appear in your dashboard with remediation steps.

Related Docker CVEs

CVE-2026-42298CVSS 10Postiz is an AI social media scheduling tool. Prior to commit da44801, a "Pwn Request" vulnerability in the Build and Publish PR Docker Image workflow (.github/workflows/pr-docker-build.yml) allows any unauthenticated user to execute arbitrary code during the Docker build process and exfiltrate a highly privileged GITHUB_TOKEN (write-all permissions). This can be achieved simply by opening a Pull Request from a fork with a maliciously modified Dockerfile.dev. This issue has been patched via commit da44801.

CVE-2026-53576CVSS 10Kestra is an open-source, event-driven orchestration platform. Prior to 1.0.45 and 1.3.21, the authentication filter for the REST API (@Filter("/api/v1/**")) treats any request whose path ends in /configs as the public instance-config endpoint and forwards it without a credential check. kestra addresses its resources by URL path segments that the caller chooses (/api/v1/{tenant}/flows/{namespace}, /api/v1/{tenant}/executions/{namespace}/{id}, /api/v1/{tenant}/namespaces/{namespace}/kv/{key}). An anonymous caller picks the literal configs as the final segment, and the request bypasses Basic-Auth entirely. Because the bypass reaches the flow-create and execution-trigger routes, an unauthenticated caller creates a flow containing a Shell or Process task and runs it. The task executes as root inside the kestra container. The official docker-compose.yml mounts /var/run/docker.sock, so root in the container reaches the host Docker daemon. This vulnerability is fixed in 1.0.45 and 1.3.21.

CVE-2026-44329CVSS 10free5GC is an open-source implementation of the 5G core network. Prior to 4.2.2, free5GC's SMF mounts the UPI management route group without OAuth2/bearer-token authorization middleware. A network attacker who can reach SMF on the SBI can hit UPI endpoints with no Authorization header at all, and the requests reach the SMF business handlers. In the running Docker lab this was directly demonstrated for read (GET /upi/v1/upNodesLinks), write (POST /upi/v1/upNodesLinks with attacker-controlled UP-node and link payload), and delete (DELETE /upi/v1/upNodesLinks/{nodeID}) operations. This vulnerability is fixed in 4.2.2.

CVE-2026-26216CVSS 10Crawl4AI versions prior to 0.8.0 contain a remote code execution vulnerability in the Docker API deployment. The /crawl endpoint accepts a hooks parameter containing Python code that is executed using exec(). The __import__ builtin was included in the allowed builtins, allowing unauthenticated remote attackers to import arbitrary modules and execute system commands. Successful exploitation allows full server compromise, including arbitrary command execution, file read and write access, sensitive data exfiltration, and lateral movement within internal networks.

CVE-2026-40281CVSS 10Gotenberg is a Docker-powered stateless API for PDF files. In versions 8.30.1 and earlier, the metadata write endpoint validates metadata keys for control characters but leaves metadata values unsanitized. A newline character in a metadata value splits the ExifTool stdin line into two separate arguments, allowing injection of arbitrary ExifTool pseudo-tags such as -FileName, -Directory, -SymLink, and -HardLink. This is a bypass of the incomplete key-sanitization fix introduced in v8.30.1. An unauthenticated attacker can rename or move any PDF being processed to an arbitrary path in the container filesystem, overwrite arbitrary files, or create symlinks and hard links at arbitrary paths.

References

Track CVEs across your fleet automatically

Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2024-6222. Free for 1 server.

Get started free