Introduction to the Kestra OSS Vulnerability

In a rapid series of updates to the Known Exploited Vulnerabilities (KEV) catalog on September 2, 2026, the Cybersecurity and Infrastructure Security Agency (CISA) added a critical flaw affecting the Kestra open-source orchestration platform. The vulnerability, identified as CVE-2026-49869, describes a remote code execution (RCE) path that requires no authentication and grants the attacker the highest level of system privileges. As automation and data orchestration platforms like Kestra become central to modern DevOps and data engineering stacks, the emergence of a “maximum severity” exploit poses a significant risk to the software supply chain and internal infrastructure.

Kestra is widely used for managing complex workflows, ranging from data pipelines to CI/CD automation. Because these platforms are designed to execute code across various environments, they are naturally high-value targets for threat actors looking to gain a foothold within a corporate network.

Understanding CVE-2026-49869

The technical root cause of CVE-2026-49869 lies in the platform’s AuthenticationFilter component. Security developers often implement filters to ensure that specific public endpoints—such as those used for configuration checks or health monitoring—remain accessible without requiring a full login. In Kestra’s case, the filter was designed to whitelist requests directed at paths ending in /configs.

The implementation error was a fundamental logic flaw: the filter used a “suffix match” rather than an “exact path match.” Consequently, an attacker could append /configs to any sensitive API endpoint path (e.g., /api/v1/executions/configs) to trick the system into bypassing the authentication check entirely. By exploiting this bypass, unauthenticated remote attackers can interact with the Kestra API as if they were authorized administrators. Most critically, they can create and trigger new workflows. Since Kestra supports powerful plugins like plugin-script-shell and plugin-script-python by default, the ability to trigger a workflow is equivalent to having the ability to execute arbitrary code on the server.

Affected Systems and Versions

The vulnerability specifically affects the Open Source Software (OSS) edition of Kestra. The flaw was introduced in early versions of the platform and persisted until recent remediation efforts. According to the vendor and security researchers at firms such as SentinelOne and Horizon3.ai, the following versions are confirmed to be vulnerable:

• Kestra OSS versions prior to 1.0.45
• Kestra OSS versions in the 1.3.x branch prior to 1.3.21

While the Kestra Enterprise Edition includes additional security layers, users are still advised to verify their deployment versions and ensure they are running patched builds to prevent any potential bypass scenarios in combined environments.

Severity Rating and Real-World Impact

CVE-2026-49869 has been assigned the maximum possible CVSS v4.0 score of 10.0 (Critical). This rating reflects several alarming factors: the exploit can be launched remotely over a network, it requires no user interaction, and it results in a total loss of confidentiality, integrity, and availability.

Furthermore, research has shown that malicious code executed through this bypass runs with root privileges (UID 0) within the Kestra worker container. For organizations running Kestra in Kubernetes or Docker environments, this creates a high risk of container escape or lateral movement into the broader cluster. CISA’s decision to add this CVE to the KEV catalog indicates that there is evidence of active exploitation in the wild, meaning threat actors are already scanning for and compromising unpatched Kestra instances to deploy reverse shells, cryptominers, or ransomware.

Immediate Mitigation and Patching Steps

Due to the critical nature of this vulnerability and the evidence of active exploitation, security teams must move immediately to secure their orchestration infrastructure. The following steps are recommended:

1. Upgrade Immediately: Deploy Kestra OSS version 1.0.45 or 1.3.21 (or any later version) as soon as possible. These releases contain the fix that changes the suffix-matching logic to a secure, exact-match validation for public endpoints.
2. Network Isolation: Ensure that your Kestra management UI and API are not exposed to the public internet. Access should be restricted to trusted internal networks or secured behind a VPN or Zero Trust Network Access (ZTNA) solution.
3. Forensic Triage: If your Kestra instance was internet-facing, assume a potential compromise. Audit the execution logs for any unfamiliar workflows or scripts. Specifically, look for unexpected usage of the shell or Python script plugins and check for unauthorized outbound network connections from your worker nodes.
4. Rotate Credentials: As a secondary precaution, rotate any API keys, database credentials, or cloud access tokens stored within Kestra’s environment variables or secrets manager, as a successful attacker could have exfiltrated these during the compromise.

Security automation is only as strong as the platform that hosts it. By securing your orchestration layer, you protect the heart of your data and deployment pipelines from one of the most severe vulnerabilities disclosed this year.