Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-38428: Kestra v1.3.3 and before is vulnerable to SQL Injection

52
This week
CRITICAL 9.8REMOTEUPGRADE

CVE-2026-38428 is a critical-severity flaw (CVSS 9.8) affecting kestra. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

  • Critical severity
  • Public exploit reference
  • Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score9.8 (Critical)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance0.4% (top 70%)
CISA exploited listNo
WeaknessCWE-89
Published2026-05-05
Last modified2026-07-24
Publisher (CNA): MITRE · Vendor: kestra

Share: LinkedIn · X · Reddit

Last updated 2026-07-24 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

kestra kestra UPGRADE
Affected: < 1.0.35 · >= 1.1.0 and < 1.3.7
Fixed in: 1.0.35, 1.3.7
Safe to downgrade to: a release before 1.1.0
1. Check installed version
apt-cache policy kestra || rpm -q kestra || kestra --version
2. UPGRADE to 1.0.35 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade kestra
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade kestra
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 1.1.0 (Debian / Ubuntu)
apt-cache madison kestra sudo apt install kestra=<VERSION_BEFORE_1.1.0> sudo apt-mark hold kestra
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list kestra sudo dnf downgrade kestra-<VERSION_BEFORE_1.1.0> sudo dnf versionlock add kestra
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-38428?

kestra: upgrade to 1.0.35, 1.3.7. Exact commands for each OS are on this page.

Is CVE-2026-38428 being exploited?

CVE-2026-38428 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-38428 affect?

CVE-2026-38428 affects kestra. Severity is critical (CVSS 9.8). 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, at

How urgent is CVE-2026-38428?

Priority 52/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.