External risk intelligence

Attackers can steal customer data or control Kestra systems.

CVE advisorySeverity: CRITICAL (CVSS 9.8)

CVE-2026-38428

An external attacker can manipulate the database in the Kestra platform by sending malicious web requests. This could allow unauthorized access to sensitive business workflows, system configurations, and stored credentials, putting proprietary data at risk.

3Halo Surface Signal

SQL Injection

Kestra

before 1.0.351.1.0 to before 1.3.7

External exposure likelihood

Halo Surface Signal score for CVE-2026-38428

Kestra is a workflow orchestration platform that typically operates as an internal tool within private networks. While it is a web application and could be exposed to the internet, such configuration is not the default or intended deployment pattern for this class of infrastructure, which is generally restricted by network controls or VPNs.

Horizon Alert

Summary of the vulnerability and why it matters

This vulnerability in Kestra allows attackers to inject malicious SQL commands by manipulating user input. This could lead to unauthorized access and modification of your sensitive data.

  • Can steal or alter data.
  • Affects systems using Kestra.
  • Accessible from the internet.

Attack Path

How an attacker could exploit the issue

An unauthenticated attacker can exploit this SQL injection flaw by sending a crafted GET request to the vulnerable Kestra application. This allows them to manipulate database queries, potentially leading to unauthorized data access, modification, or deletion.

  • Attacker needs network access.
  • Targets web interface GET parameter.
  • No authentication required.

Live Threat

Current exploitation, exposure, and threat context

SQL injection vulnerabilities are attractive to attackers due to their potential for broad impact, including data theft, modification, and denial of service. This specific vulnerability in Kestra is accessible via the network without authentication, making it a prime target if the application is exposed. While the platform is often used internally, any internet-facing deployment significantly increases its risk profile.

  • No immediate KEV signals.
  • Public exploit code availability is uncertain.
  • Recency is implied by recent modification date.

Priority actions

Operational Fix

Recommended remediation, mitigation, and detection steps

Teams should prioritize investigating Kestra instances for signs of SQL injection attempts and isolating any confirmed compromised services. Focus on identifying and blocking the source of malicious SQL payloads targeting GET parameters.

  • Block SQL injection traffic.
  • Isolate or take affected services offline.
  • Monitor for unauthorized data access.

Frequently asked questions

What is Kestra and what is it used for?

Kestra is a workflow orchestration platform. It is used to design, schedule, and orchestrate complex data pipelines and automation tasks. This helps organizations manage and automate their data-related processes efficiently.

What kind of vulnerability does CVE-2026-38428 represent?

CVE-2026-38428 is a SQL Injection vulnerability. This means attackers can insert malicious SQL code into queries, potentially allowing them to steal, modify, or delete data within the Kestra application's database.

How can an attacker exploit this Kestra vulnerability?

An attacker can exploit this vulnerability by sending a specially crafted GET request to the Kestra application. They would manipulate a GET parameter to inject SQL commands, bypassing security measures and interacting directly with the database without needing to authenticate.

Who should be concerned about this Kestra vulnerability?

Organizations using Kestra should be concerned, especially if their Kestra instances are accessible from the internet. While Kestra is often used internally, any internet-facing deployment presents a significant risk due to the ease of exploitation.

What is the first step to respond to this Kestra vulnerability?

The first step is to investigate your Kestra instances for any signs of SQL injection attempts. If you find any evidence of exploitation, you should immediately isolate the affected services to prevent further damage or data compromise.

References