high CVSS 8.8

CVE-2026-54232·Docker vulnerability

vLLM is an inference and serving engine for large language models (LLMs). Prior to 0.22.1, the vLLM Dockerfile is vulnerable to a dependency confusion attack through the flashinfer-jit-cache package. The package is installed from a custom index (flashinfer.ai/whl/) using --extra-index-url, but the package name was not registered on PyPI, and UV_INDEX_STRATEGY="unsafe-best-match" is set globally. An attacker who registers flashinfer-jit-cache on PyPI with version 0.6.11.post2 can execute arbitrary code as root during the Docker build and backdoor every resulting container image, enabling exfiltration of all user prompts, API credentials, and model data from production vLLM deployments This vulnerability is fixed in 0.22.1.

Severity
high
Software
Docker
Fixed in
0.22.1
Published
2026-06-22

Affected versions

Until: 0.22.1

Fixed in: 0.22.1

How to fix this CVE

Update Docker to the latest version that includes the patched vLLM component (0.22.1 or later). This vulnerability stems from a dependency confusion attack targeting the vLLM inference engine's build process, where an attacker could inject malicious code during container image creation. Immediately rebuild all Docker images created with vulnerable vLLM versions to prevent backdoored containers from running in production.

sudo dnf update docker-ce

Defensia detects this vulnerability

How to check if you are affected

  1. Check Docker version: docker --version
  2. List all Docker images and their creation timestamps: docker images --no-trunc --format '{{.Repository}}:{{.Tag}} {{.CreatedAt}}'
  3. For each image, inspect vLLM version in the Dockerfile history: docker history <image-id> | grep -i vllm
  4. Verify the vLLM version inside running containers: docker exec <container-id> pip show vllm | grep Version
  5. Check container build logs for flashinfer-jit-cache package installation: docker inspect <image-id> | grep -A 20 'flashinfer'

Indicators of compromise

  • PyPI package: flashinfer-jit-cache version 0.6.11.post2
  • Docker image layer containing vLLM version < 0.22.1
  • Dockerfile RUN command with 'flashinfer.ai/whl/' index URL

FAQ

What is CVE-2026-54232?

CVE-2026-54232 is a dependency confusion vulnerability in vLLM's Docker build process where an attacker can register a malicious package on PyPI with the same name as a private dependency, allowing arbitrary code execution as root during container image creation and potential backdooring of production deployments.

Is CVE-2026-54232 being actively exploited?

According to CISA's Known Exploited Vulnerabilities list, CVE-2026-54232 is not currently being actively exploited in the wild, and no public exploits are available. However, the attack vector is straightforward and organizations should prioritize remediation.

What versions of Docker are affected by CVE-2026-54232?

Docker installations running vLLM versions prior to 0.22.1 are affected. Any container image built with vulnerable vLLM code remains at risk until rebuilt with the patched version.

How do I check if my server is vulnerable to CVE-2026-54232?

Run 'docker images' to list all images, then for each image execute 'docker inspect <image-id>' and search for vLLM version in the layers. If vLLM version is below 0.22.1, the image is vulnerable.

Does Defensia detect CVE-2026-54232?

Yes — Defensia's CVE advisory scanner compares installed Docker package versions and detects vLLM versions within container images against the NVD database. If vulnerable images are present on a monitored server, CVE-2026-54232 will appear in your dashboard with remediation steps.

Related Docker CVEs

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-57572CVSS 10Crawl4AI is an open-source LLM-friendly web crawler and scraper. Prior to 0.9.0, the Docker API server accepted request-supplied browser_config.extra_args, which flowed into Chromium's launch arguments. An attacker could inject Chromium switches that replace a child-process launch command together with --no-zygote, causing Chromium to fork or exec an attacker-controlled command as the container's runtime user. The Docker API is unauthenticated by default, so a single request yields arbitrary command execution. This issue is fixed in version 0.9.0.
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.
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-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.

References

Track CVEs across your fleet automatically

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

Get started free