high CVSS 7.5

CVE-2026-28479·Docker vulnerability

OpenClaw versions prior to 2026.2.15 use SHA-1 to hash sandbox identifier cache keys for Docker and browser sandbox configurations, which is deprecated and vulnerable to collision attacks. An attacker can exploit SHA-1 collisions to cause cache poisoning, allowing one sandbox configuration to be misinterpreted as another and enabling unsafe sandbox state reuse.

Severity
high
Software
Docker
Fixed in
2026.2.15
Published
2026-03-05

Affected versions

Until: 2026.2.15

Fixed in: 2026.2.15

How to fix this CVE

Update Docker to version 2026.2.15 or later to replace the deprecated SHA-1 hashing algorithm with a collision-resistant alternative for sandbox identifier cache keys. This patch prevents attackers from poisoning the sandbox configuration cache and forcing unsafe state reuse between isolated containers. Prioritize this update for systems running Docker in multi-tenant or high-security environments where sandbox isolation is critical.

sudo dnf update docker-ce

Defensia detects this vulnerability

How to check if you are affected

  1. Run 'docker version' or 'docker --version' to check the installed Docker version; confirm it is 2026.2.15 or later
  2. Verify sandbox configuration caching is enabled by checking Docker daemon logs with 'journalctl -u docker -n 100 | grep sandbox' for cache-related entries
  3. Search system logs for cache collision or configuration mismatch errors using 'grep -r "cache.*poison\|collision" /var/log/docker* /var/log/syslog' to detect exploitation attempts
  4. After patching, restart the Docker daemon with 'sudo systemctl restart docker' and re-run 'docker version' to confirm the fix is active

FAQ

What is CVE-2026-28479?

CVE-2026-28479 is a cache poisoning vulnerability in Docker's sandbox isolation mechanism caused by use of the cryptographically weak SHA-1 algorithm for hashing sandbox identifiers. An attacker can craft colliding cache keys to force one sandbox configuration to be mistaken for another, potentially allowing escape or privilege escalation in containerized environments.

Is CVE-2026-28479 being actively exploited?

No, this vulnerability is not currently listed on the CISA Known Exploited Vulnerabilities (KEV) catalog and no public exploits are available. However, the low complexity of exploitation makes proactive patching important for defense-in-depth.

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

All versions of Docker prior to 2026.2.15 are affected. The vulnerability exists in the OpenClaw sandbox component used by Docker. Update to 2026.2.15 or later to remediate.

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

Run 'docker --version' and compare the output to 2026.2.15. If your version is earlier, your system is vulnerable. You can also run 'docker inspect <container-id> | grep -i sandbox' to verify sandbox configuration caching is in use.

Does Defensia detect CVE-2026-28479?

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

Related Docker CVEs

CVE-2026-33587CVSS 10Lack of user input sanitisation in Open Notebook v1.8.3 allows the application user to execute Python code (and subsequently OS commands) on the docker container via Server-Side Template Injection (SSTI) for user-created transformations.
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-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-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-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-28479. Free for 1 server.

Get started free