critical CVSS 9.8

CVE-2026-23944·Docker vulnerability

Arcane is an interface for managing Docker containers, images, networks, and volumes. Prior to version 1.13.2, unauthenticated requests could be proxied to remote environment agents, allowing access to remote environment resources without authentication. The environment proxy middleware handled `/api/environments/{id}/...` requests for remote environments before authentication was enforced. When the environment ID was not local, the middleware proxied the request and attached the manager-held agent token, even if the caller was unauthenticated. This enabled unauthenticated access to remote environment operations (e.g., listing containers, streaming logs, or other agent endpoints). An unauthenticated attacker could access and manipulate remote environment resources via the proxy, potentially leading to data exposure, unauthorized changes, or service disruption. Version 1.13.2 patches the vulnerability.

Severity
critical
Software
Docker
Fixed in
1.13.2
Published
2026-01-19

Affected versions

Until: 1.13.2

Fixed in: 1.13.2

How to fix this CVE

Upgrade Docker to version 1.13.2 or later to patch an authentication bypass in the environment proxy middleware. Prior versions allowed unauthenticated attackers to access remote environment resources by proxying requests without proper credential validation. Apply the update immediately to prevent unauthorized access to container operations and remote resources.

sudo dnf update docker-ce

Defensia detects this vulnerability

What an exploitation attempt looks like

Sample log line indicative of exploitation attempts:

POST|GET /api/environments/[a-f0-9-]{36}/[^\s]+ HTTP/1\.[01] .{0,500}(401|403|Unauthorized) response absent; successful container list, image pull, or log stream operations without Bearer token in Authorization header

WAF mitigation (if patching is not yet possible)

Add this rule to your WAF to block exploitation attempts while you schedule the patch. 

Implement authentication enforcement before routing /api/environments/{id}/* requests to proxy handlers. Block requests to this endpoint path that lack valid Bearer token or session cookie credentials. Enforce origin validation to prevent cross-environment token reuse.

How to check if you are affected

  1. Check the installed Docker version: docker --version
  2. Verify if Arcane environment proxy is enabled: grep -r 'environment.*proxy' /etc/docker/ /var/lib/docker/config/ 2>/dev/null
  3. Search Docker daemon logs for unauthenticated proxy requests: journalctl -u docker -S '24 hours ago' | grep -E '(unauthenticated|proxy|/api/environments)' | head -20
  4. Confirm the patch is applied: docker --version | grep -E '(1\.13\.[2-9]|1\.(14|15|16))' && echo 'Patched' || echo 'Vulnerable'

FAQ

What is CVE-2026-23944?

CVE-2026-23944 is a critical authentication bypass vulnerability in Docker's Arcane environment proxy middleware that allows unauthenticated attackers to access and manipulate remote environment resources, including containers, logs, and volumes, by proxying API requests with elevated credentials.

Is CVE-2026-23944 being actively exploited?

No, there are no confirmed reports of active exploitation or publicly available exploits, but the critical CVSS score (9.8) and simplicity of the attack vector make immediate patching essential.

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

All versions prior to 1.13.2 are affected; Docker versions 1.13.2 and later contain the security patch.

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

Run 'docker --version' and compare the version number. If it is below 1.13.2, your installation is vulnerable. Additionally, check if unauthenticated requests to /api/environments/{id}/... endpoints return 200 responses instead of 401 Unauthorized.

Does Defensia detect CVE-2026-23944?

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

Related Docker CVEs

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-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.
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-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-2026-23944. Free for 1 server.

Get started free