CVE-2026-38428: n/a
Kestra versions 1.3.3 and earlier are affected by a critical SQL Injection vulnerability due to improper sanitization of user input in a GET parameter. This allows attackers to inject arbitrary SQL code into database queries, potentially leading to full compromise of confidentiality, integrity, and availability of the affected system. The vulnerability has a CVSS score of 9.8, indicating a critical severity level. No official patch or remediation guidance is currently available from the vendor. There are no known exploits in the wild at this time.
AI Analysis
Technical Summary
CVE-2026-38428 describes a critical SQL Injection vulnerability in Kestra v1.3.3 and earlier. The issue arises because user-controlled input from a GET parameter is concatenated directly into an SQL query without proper sanitization or parameterization, enabling attackers to inject arbitrary SQL expressions. This vulnerability is classified under CWE-89 and has a CVSS v3.1 base score of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), reflecting its high impact on confidentiality, integrity, and availability. No patch or official remediation has been disclosed, and the product is not a cloud service, so remediation depends on vendor or user action.
Potential Impact
Successful exploitation of this vulnerability can lead to full compromise of the affected Kestra system's database, including unauthorized data disclosure, data modification, and denial of service. The critical CVSS score reflects the ease of exploitation (network attack vector, no privileges or user interaction required) and the severe impact on confidentiality, integrity, and availability. There are no known active exploits reported at this time.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, users should consider implementing temporary mitigations such as input validation, web application firewalls (WAFs) with SQL injection protections, or disabling vulnerable functionality if feasible. Monitor vendor channels closely for updates and patches.
CVE-2026-38428: n/a
Description
Kestra versions 1.3.3 and earlier are affected by a critical SQL Injection vulnerability due to improper sanitization of user input in a GET parameter. This allows attackers to inject arbitrary SQL code into database queries, potentially leading to full compromise of confidentiality, integrity, and availability of the affected system. The vulnerability has a CVSS score of 9.8, indicating a critical severity level. No official patch or remediation guidance is currently available from the vendor. There are no known exploits in the wild at this time.
CVSS v3.1
Score 9.8critical
Affected software
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-38428 describes a critical SQL Injection vulnerability in Kestra v1.3.3 and earlier. The issue arises because user-controlled input from a GET parameter is concatenated directly into an SQL query without proper sanitization or parameterization, enabling attackers to inject arbitrary SQL expressions. This vulnerability is classified under CWE-89 and has a CVSS v3.1 base score of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), reflecting its high impact on confidentiality, integrity, and availability. No patch or official remediation has been disclosed, and the product is not a cloud service, so remediation depends on vendor or user action.
Potential Impact
Successful exploitation of this vulnerability can lead to full compromise of the affected Kestra system's database, including unauthorized data disclosure, data modification, and denial of service. The critical CVSS score reflects the ease of exploitation (network attack vector, no privileges or user interaction required) and the severe impact on confidentiality, integrity, and availability. There are no known active exploits reported at this time.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, users should consider implementing temporary mitigations such as input validation, web application firewalls (WAFs) with SQL injection protections, or disabling vulnerable functionality if feasible. Monitor vendor channels closely for updates and patches.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- mitre
- Date Reserved
- 2026-04-06T00:00:00.000Z
- Cvss Version
- null
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69fa3543cbff5d8610191209
Added to database: 5/5/2026, 6:21:55 PM
Last enriched: 5/13/2026, 3:47:30 AM
Last updated: 6/20/2026, 7:02:14 AM
Views: 76
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.