dbcve.org
KestraApplication

CVE-2026-38428

CRITICAL · 9.8 CVSS v3.1 Published 2026-05-05
Fix available
A fix is available. Upgrade to 1.0.35 / 1.3.7 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Kestra v1.3.3 and earlier contains a SQL injection vulnerability where user-controlled input from a GET parameter is directly concatenated into an SQL query without sanitization or parameterization, allowing attackers to inject arbitrary SQL expressions.

MitigationReplace direct string concatenation with parameterized queries (prepared statements) for all database queries that incorporate user input, and implement input validation and whitelisting for GET parameters.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
KestraApplication
Affected:< 1.0.35>= 1.1.0, < 1.3.7

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Kestra is installed
    Look for Kestra installation directories, Docker containers, or running processes. Check common locations like /opt/kestra, /usr/local/kestra, or search for 'kestra' in running processes.
    Affected if Kestra software is present on the system
  2. Identify installed Kestra version
    Check the version file or CLI output. Run 'kestra --version' if CLI is available, or check version files in the installation directory such as VERSION, build.gradle, or the jar file manifest.
    Affected if Version cannot be determined or is below 1.0.35, or between 1.1.0 and 1.3.6 inclusive
  3. Compare version against affected ranges
    The affected versions are: < 1.0.35, and >= 1.1.0 but < 1.3.7. If your version is 1.0.34 or lower, 1.1.0 through 1.3.6, or 1.3.3 specifically, you are in the affected range.
    Affected if Installed version falls within < 1.0.35 or >= 1.1.0 and < 1.3.7
  4. Determine if web/API interface is exposed
    Check server configuration files (application.yml, application.properties) for server.address, server.port settings, or look for reverse proxy configurations that expose the Kestra API. Verify if port 8080 or configured HTTP port is accessible from network.
    Affected if Kestra HTTP server is bound to a reachable address and port, allowing external GET parameter input
  5. Identify vulnerable GET parameter endpoints
    Review application logs or API documentation for endpoints that accept GET query parameters and interact with the database. The vulnerability involves direct SQL concatenation of GET parameters.
    Affected if Any GET endpoints that accept user input and construct SQL queries without parameterized prepared statements are in use

You are affected if Kestra is running with a version in the range < 1.0.35 or >= 1.1.0 to < 1.3.7 and has its web/API interface accessible, as the SQL injection requires both a vulnerable version and the ability to send GET requests to the application.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.0.35 / 1.3.7 or later
Fixed in 1.0.351.3.7
Interim mitigation

Replace direct string concatenation with parameterized queries (prepared statements) for all database queries that incorporate user input, and implement input validation and whitelisting for GET parameters.

Recommended fix Moderate confidence

Kestra 1.0.35 (for 1.0.x branch) or Kestra 1.3.7+ (for 1.1.x-1.3.x branch)

  1. Identify the currently running Kestra version in your environment
  2. For Kestra 1.0.x branch: upgrade to version 1.0.35 or later
  3. For Kestra 1.1.x - 1.3.x branch: upgrade to version 1.3.7 or later
  4. After upgrade, verify the SQL injection vulnerability is resolved by testing the affected GET parameter endpoint
  5. Ensure proper backup of database before performing upgrade in production
Caveat Review Kestra release notes between your current version and target version for any breaking changes or migration requirements

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Kestra Scoped from the published advisory
  • Consultation8.0 h
  • Implementation40.0 h
  • Testing16.0 h
  • Review / QA8.0 h
72.0 hours of engineering $12,640
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $20,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-38428 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-38428 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data