CVE-2026-34612
SQL Injection in Kestra Docker Leads to Remote Code Execution
Publication date: 2026-04-03
Last updated on: 2026-04-13
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| kestra | kestra | to 1.3.7 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
Kestra is an open-source, event-driven orchestration platform. Prior to version 1.3.7, the default docker-compose deployment of Kestra contains a SQL Injection vulnerability in the endpoint "GET /api/v1/main/flows/search". Once a user is authenticated, simply visiting a specially crafted link can trigger this vulnerability. The injected SQL payload is executed by PostgreSQL using the COPY ... TO PROGRAM ... command, which allows arbitrary operating system commands to be run on the host machine.
This vulnerability has been fixed in Kestra version 1.3.7.
How can this vulnerability impact me? :
This vulnerability can have severe impacts because it allows an authenticated user to execute arbitrary operating system commands on the host running Kestra. This means an attacker could potentially take full control of the system, leading to data theft, data loss, service disruption, or further compromise of the network.
What immediate steps should I take to mitigate this vulnerability?
The vulnerability has been patched in Kestra version 1.3.7. The immediate step to mitigate this vulnerability is to upgrade Kestra to version 1.3.7 or later.