Findings

CVE-2026-38428

Kestra v1.3.3 and before is vulnerable to SQL Injection.

Published May 5, 2026 · updated Jul 24, 2026 · kestra kestra

Kestra v1.3.3 and before is vulnerable to SQL Injection. The vulnerability occurs because user-controlled input from a GET parameter is directly concatenated into an SQL query without proper sanitization or parameterization. As a result, attackers can inject arbitrary SQL expressions into the database query.

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. May 5, 2026 · NIST NVD

    Detected

    Kestra v1.3.3 and before is vulnerable to SQL Injection. The vulnerability occurs because user-controlled input from a GET parameter is directly concatenated into an SQL query without proper sanitization or parameterization. As a result, attackers can inject arbitrary SQL expressions into the database query.

  2. Jul 24, 2026 · NIST NVD

    Updated

    Kestra v1.3.3 and before is vulnerable to SQL Injection. The vulnerability occurs because user-controlled input from a GET parameter is directly concatenated into an SQL query without proper sanitization or parameterization. As a result, attackers can inject arbitrary SQL expressions into the database query.

Affected

  • cpe kestra/kestraversion unspecified

Sources

  • CVE.orgVulnerability recordCVE-2026-38428

    Official CVE identifier

    cve.org
  • NIST NVDVulnerability recordCVE-2026-38428

    Kestra v1.3.3 and before is vulnerable to SQL Injection. The vulnerability occurs because user-controlled input from a GET parameter is directly concatenated into an SQL query without proper sanitization or parameterization. As a result, attackers can inject arbitrary SQL express

    nvd.nist.gov

References

CVE-2026-38428 · ZeroDay Findings