critical CVSS 9.8

CVE-2025-69201·Docker vulnerability

Tugtainer is a self-hosted app for automating updates of docker containers. In versions prior to 1.15.1, arbitary arguments can be injected in tugtainer-agent `POST api/command/run`. Version 1.15.1 fixes the issue.

Severity
critical
Software
Docker
Fixed in
1.15.1
Published
2025-12-29

Affected versions

Until: 1.15.1

Fixed in: 1.15.1

How to fix this CVE

Tugtainer versions before 1.15.1 contain a critical command injection vulnerability in the tugtainer-agent API endpoint that allows unauthenticated attackers to execute arbitrary commands on the host system. Immediately upgrade Tugtainer to version 1.15.1 or later, which implements proper input sanitization and argument validation to prevent command injection attacks.

sudo dnf update docker-ce

Defensia detects this vulnerability

What an exploitation attempt looks like

Sample log line indicative of exploitation attempts:

POST /api/command/run HTTP/1.1.*Content-Type: application/json.*;.*bash.*|.*sh.*|.*exec.*|.*eval.*|.*nc.*|.*cat.*|.*wget.*|.*curl

WAF mitigation (if patching is not yet possible)

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

Implement strict input validation on the /api/command/run POST endpoint to reject payloads containing shell metacharacters (;|&|`|$|\n|\r|>) and command substitution patterns ($()|``). Enforce rate limiting on API endpoints and require authentication before accepting command execution requests.

How to check if you are affected

  1. Check Tugtainer version: docker inspect tugtainer-agent 2>/dev/null | grep -i version || curl -s http://localhost:3000/api/version 2>/dev/null || grep -r 'VERSION\|version' /opt/tugtainer/package.json 2>/dev/null
  2. Verify if tugtainer-agent is exposed to untrusted networks: netstat -tuln | grep -E ':(3000|8080)' or docker ps | grep tugtainer-agent
  3. Search container and application logs for suspicious POST requests to /api/command/run endpoint: grep -i 'POST.*api/command/run' /var/log/containers/*.log /var/log/docker/*.log 2>/dev/null
  4. Confirm remediation by checking installed Tugtainer version is 1.15.1 or later: docker exec tugtainer-agent cat /app/package.json | grep version || curl -s http://localhost:3000/api/version | jq '.version'

FAQ

What is CVE-2025-69201?

CVE-2025-69201 is a critical command injection vulnerability in Tugtainer's REST API that allows remote attackers to inject arbitrary shell arguments into the tugtainer-agent POST /api/command/run endpoint without authentication, leading to complete system compromise.

Is CVE-2025-69201 being actively exploited?

No, CVE-2025-69201 is not currently listed in CISA's Known Exploited Vulnerabilities catalog and no public exploits have been released, but the critical CVSS 9.8 score and ease of exploitation warrant immediate patching.

What versions of Docker are affected by CVE-2025-69201?

This vulnerability affects Tugtainer (a Docker container update automation tool) versions prior to 1.15.1, not Docker itself. All versions below 1.15.1 are vulnerable.

How do I check if my server is vulnerable to CVE-2025-69201?

Run 'docker ps | grep tugtainer' to identify if Tugtainer is deployed, then check the version with 'docker exec tugtainer-agent cat /app/package.json | grep version'. If the version is below 1.15.1, you are vulnerable.

Does Defensia detect CVE-2025-69201?

Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Tugtainer is installed on a monitored server, CVE-2025-69201 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-2025-69201. Free for 1 server.

Get started free