critical CVSS 9.9

CVE-2026-34612·Docker vulnerability

Kestra is an open-source, event-driven orchestration platform. Prior to version 1.3.7, Kestra (default docker-compose deployment) contains a SQL Injection vulnerability that leads to Remote Code Execution (RCE) in the following endpoint "GET /api/v1/main/flows/search". Once a user is authenticated, simply visiting a crafted link is enough to trigger the vulnerability. The injected payload is executed by PostgreSQL using COPY ... TO PROGRAM ..., which in turn runs arbitrary OS commands on the host. This issue has been patched in version 1.3.7.

Severity
critical
Software
Docker
Fixed in
1.3.7
Published
2026-04-03

Affected versions

Until: 1.3.7

Fixed in: 1.3.7

How to fix this CVE

Upgrade Docker to version 1.3.7 or later to patch the SQL injection vulnerability in the Kestra orchestration platform. This vulnerability allows authenticated users to execute arbitrary OS commands through a crafted URL to the /api/v1/main/flows/search endpoint. Immediate patching is critical due to the critical severity rating and the potential for complete system compromise.

sudo dnf update docker-ce

Defensia detects this vulnerability

What an exploitation attempt looks like

Sample log line indicative of exploitation attempts:

GET /api/v1/main/flows/search.*(%27|%22|%27%20OR|%27;|COPY|TO%20PROGRAM|union|select|exec|\x27)

WAF mitigation (if patching is not yet possible)

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

Block or rate-limit requests to /api/v1/main/flows/search endpoint containing SQL metacharacters (single quotes, semicolons, SQL keywords like UNION, COPY, PROGRAM) in query parameters. Implement strict input validation and parameterized queries at the application layer. Require authentication and apply Web Application Firewall rules to detect and block SQL injection patterns in authenticated requests.

How to check if you are affected

  1. Run 'docker --version' to check the installed Docker version and confirm it is 1.3.7 or later
  2. Check if Kestra is deployed via Docker Compose by looking for docker-compose.yml files and verify the Kestra service image tag using 'docker images | grep kestra'
  3. Review PostgreSQL query logs for suspicious COPY ... TO PROGRAM statements by checking '/var/lib/postgresql/data/log/' or container logs with 'docker logs {container_id} | grep COPY'
  4. Verify the patch by checking the Kestra service logs for version confirmation: 'docker exec {kestra_container} grep -i version /app/version.txt' or restart the container and confirm no SQL injection errors appear

FAQ

What is CVE-2026-34612?

CVE-2026-34612 is a critical SQL injection vulnerability in Kestra versions prior to 1.3.7 that allows authenticated users to execute arbitrary operating system commands on the host by visiting a specially crafted URL, exploiting PostgreSQL's COPY TO PROGRAM functionality.

Is CVE-2026-34612 being actively exploited?

No, CVE-2026-34612 is not currently listed on the CISA Known Exploited Vulnerabilities (KEV) catalog and no public exploit code has been released, but the critical severity and ease of exploitation warrant immediate patching.

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

All Kestra versions prior to 1.3.7 deployed in Docker environments are affected; the vulnerability resides in Kestra itself rather than Docker, but exploitation occurs within Docker-deployed instances.

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

Run 'docker images | grep kestra' and verify the tag version; if it is below 1.3.7, your deployment is vulnerable. Additionally, check for the presence of the vulnerable endpoint by testing access to '/api/v1/main/flows/search'.

Does Defensia detect CVE-2026-34612?

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

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

Get started free