critical CVSS 9.9

CVE-2025-23211·Docker vulnerability

Tandoor Recipes is an application for managing recipes, planning meals, and building shopping lists. A Jinja2 SSTI vulnerability allows any user to execute commands on the server. In the case of the provided Docker Compose file as root. This vulnerability is fixed in 1.5.24.

Severity
critical
Software
Docker
Fixed in
1.5.24
Published
2025-01-28

Affected versions

Until: 1.5.24

Fixed in: 1.5.24

How to fix this CVE

Update Docker to version 1.5.24 or later to patch a critical server-side template injection vulnerability in Tandoor Recipes that allows authenticated users to execute arbitrary commands. Immediately apply this update to all Docker hosts, especially those running containerized recipe management applications. Verify the update completion and restart affected containers to ensure the patched version is active.

sudo dnf update docker-ce

Defensia detects this vulnerability

What an exploitation attempt looks like

Sample log line indicative of exploitation attempts:

POST /api/recipe|GET /recipe.*{{.*}}|Template syntax patterns like {{7*7}}, {%.*%}, or {{config.__class__}} in HTTP request body or parameters; Jinja2 error messages appearing in application responses indicating template processing of user input

WAF mitigation (if patching is not yet possible)

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

Block HTTP requests containing suspicious Jinja2 template syntax in POST/GET parameters using regex pattern: (?:{{|{%|\[\[)[^}]*(?:}}|%}|\]\]) . Implement strict input validation on recipe fields and disable dynamic template rendering from user-supplied input.

How to check if you are affected

  1. Run 'docker --version' to check your current Docker installation version; versions below 1.5.24 are vulnerable
  2. Verify if Tandoor Recipes containers are running by executing 'docker ps | grep -i recipe' or checking your docker-compose.yml for recipe services
  3. Search container logs for SSTI payloads using 'docker logs <container_id> | grep -E "{{.*}}|jinja|template"' to identify exploitation attempts
  4. Confirm the patch is applied by re-running 'docker --version' and verifying the version is 1.5.24 or higher

FAQ

What is CVE-2025-23211?

This is a Server-Side Template Injection (SSTI) vulnerability in Tandoor Recipes running within Docker containers. Authenticated users can inject malicious Jinja2 template syntax to execute arbitrary system commands with the privileges of the container process.

Is CVE-2025-23211 being actively exploited?

No, this vulnerability is not listed on the CISA Known Exploited Vulnerabilities (KEV) catalog and no public exploits are currently available. However, the critical CVSS score of 9.9 warrants immediate patching regardless of active exploitation status.

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

All versions of Docker prior to 1.5.24 are affected. The vulnerability exists in Tandoor Recipes' template handling logic, affecting any Docker deployment running vulnerable versions of the recipe management application.

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

Run 'docker --version' to check your Docker version. If the version is below 1.5.24, your installation is vulnerable. Additionally, inspect running containers with 'docker inspect <container_id> | grep -i image' to confirm if Tandoor Recipes is deployed.

Does Defensia detect CVE-2025-23211?

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

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

Get started free