Is CVE-2026-34612 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-34612 being exploited in the wild.

How severe is CVE-2026-34612?

Critical severity, with a CVSS score of 9.9, published 3 April 2026.

Is there a fix for CVE-2026-34612?

A patch was published on 2026-03-30: Fix committed to repository Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-34612 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-34612?

Check whether you run Kestra at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-34612: Kestra SQL injection in flow search leads to RCE

CVE-2026-34612 · Severity: critical · CVSS 9.9 · Published 2026-04-03

Kestra is an open-source platform used by businesses to automate and orchestrate complex data workflows. A security flaw in the platform's search feature allows an authenticated user to execute unauthorized commands on the underlying server by clicking a specially crafted link. This could lead to a total system takeover, theft of sensitive operational data, or disruption of automated business processes.

Technologies: Kestra. Vendors: Kestra.

Quick answers

Is CVE-2026-34612 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-34612 being exploited in the wild.
How severe is CVE-2026-34612?: Critical severity, with a CVSS score of 9.9, published 3 April 2026.
Which products and versions are affected?: Kestra < 1.3.7.
Is there a fix for CVE-2026-34612?: A patch was published on 2026-03-30: Fix committed to repository Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-34612 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-34612?: Check whether you run Kestra at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A SQL injection vulnerability exists in the 'GET /api/v1/main/flows/search' endpoint due to improper neutralization of the 'labels' filter parameters. In the 'PostgresFlowRepositoryService.findCondition' method, label keys and values are concatenated directly into a JSONB containment expression string without parameter binding. An attacker can break out of the JSON string to execute stacked queries. In the default Docker deployment using PostgreSQL, this is escalated to Remote Code Execution (RCE) via the 'COPY ... TO PROGRAM' command. The vulnerability also affects H2-backed deployments via 'FILE_WRITE()'. Exploitation requires authentication but can be triggered via a crafted link (Cross-Site Request Forgery style). The issue is patched in version 1.3.7.

Affected products

kestra-io Kestra < 1.3.7

Timeline

2026-03-30: advisory: Internal advisory published by vendor
2026-03-30: patched: Fix committed to repository
2026-04-01: patched: Version 1.3.7 released
2026-04-03: disclosed: CVE published to NVD

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.