CVE-2026-49869
Kestra OSS OS Command Injection Vulnerability
Description
CVE-2026-49869 is a maximum-severity authentication bypass leading to unauthenticated remote code execution in Kestra OSS, the open-source event-driven orchestration platform. Prior to versions 1.0.45 and 1.3.21, AuthenticationFilter used request.getPath().endsWith("/configs") to whitelist the public configuration endpoint from Basic Auth; because the check is a suffix match rather than an exact path match, any API path whose last segment is configs bypasses authentication entirely. An unauthenticated remote attacker can exploit this to create and execute arbitrary workflows without credentials, and since Kestra ships with script execution plugins such as plugin-script-shell and plugin-script-python enabled by default, this directly results in remote code execution as root inside the Kestra worker container. CVE-2026-49869 carries the maximum CVSS score of 10.0, is fixed in 1.0.45 and 1.3.21, and is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.
KEV Information
CVSS Score
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:HOpen in CalculatorCWEs
Affected Products
| Vendor | Product | Version |
|---|---|---|
| kestra | kestra | < 1.0.45; >= 1.1.0, < 1.3.21 |
References
- https://github.com/kestra-io/kestra/security/advisories/GHSA-5vc5-wxxq-3fjx(Exploit, Vendor Advisory)
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-49869(US Government Resource)
Weakness Type
CWE-287: Improper Authentication
Improper authentication occurs when software fails to properly prove that an actor holds the identity they claim, including cases where a flawed exemption rule lets a request skip the check. In CVE-2026-49869 Kestra's AuthenticationFilter exempts requests from Basic Auth based on a suffix match for /configs, so any attacker-chosen API path ending in that segment is admitted without credentials.
Learn more: CWE-287 — Improper Authentication
CWE-184: Incomplete List of Disallowed Inputs
This weakness covers protection logic built around an incomplete or imprecise set of accepted or rejected inputs, so variants outside the intended set slip through. The endsWith("/configs") whitelist is exactly that: it was meant to describe one specific public endpoint, but as a suffix test it matches an open-ended family of paths the author never intended to expose.
Learn more: CWE-184 — Incomplete List of Disallowed Inputs
CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
OS command injection occurs when software builds an operating system command from externally influenced input without neutralising special elements that change the command's meaning. In Kestra the consequence is more direct than classic injection: once authentication is bypassed, the attacker creates workflows that legitimately invoke the bundled shell and Python script plugins, so operating system commands of their choosing execute as root inside the worker container.
Learn more: CWE-78 — Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
CWE-918: Server-Side Request Forgery (SSRF)
SSRF occurs when an application fetches a remote resource from a user-supplied URL without validation, letting an attacker coerce the server into contacting unintended destinations, including internal systems behind a firewall. An orchestration platform executing attacker-defined workflows can be directed to issue requests from its own trusted network position, turning the Kestra worker into a proxy into otherwise unreachable internal services.
Learn more: CWE-918 — Server-Side Request Forgery (SSRF)
Impact Analysis
CVE-2026-49869 reaches the maximum CVSS 3.1 base score of 10.0 because it is remotely exploitable over the network with low attack complexity, no authentication, no user interaction and a CHANGED scope — the attack escapes the web API and executes code in the worker container. Confidentiality, integrity and availability impacts are all High: root-level execution inside a Kestra worker exposes every credential, connection string and secret the orchestration platform uses to reach databases, cloud accounts and internal services, allows arbitrary modification of the workflows an organisation relies on, and permits destruction of the environment. Orchestration platforms are high-value targets precisely because they are deliberately wired into everything else, so a single unauthenticated request chain converts into broad access across the estate. The EPSS score of roughly 1.9% places it in the 79th percentile, and CISA's KEV listing set a remediation deadline of 5 September 2026 that has already passed.
Exploit Maturity
CISA has confirmed active exploitation of CVE-2026-49869 by adding it to the Known Exploited Vulnerabilities catalog with a remediation deadline of 5 September 2026, which has already passed. The vendor's GitHub Security Advisory GHSA-5vc5-wxxq-3fjx is tagged as exploit material and describes the flawed endsWith("/configs") check in full, which for a logic bug of this kind is effectively complete exploitation guidance — no memory-corruption skill is needed, only appending a path segment. The EPSS score of about 1.9% places it in the 79th percentile, consistent with broad opportunistic scanning. The KEV ransomware flag is "Unknown", but unauthenticated root execution on a system holding an organisation's orchestration credentials is exactly the profile ransomware affiliates seek, so any Kestra instance that was exposed while unpatched warrants a full compromise assessment rather than a patch alone.
Remediation
- Follow the CISA KEV required action immediately. Apply mitigations in accordance with the vendor's instructions, comply with CISA's BOD 26-04 "Prioritizing Security Updates Based on Risk" guidance and the "Forensics Triage Requirements", and discontinue use of the product if mitigations are unavailable. The KEV due date of 5 September 2026 has passed.
- Upgrade Kestra to 1.0.45 or 1.3.21 or later. Affected versions are all releases before 1.0.45 and the 1.1.0 through 1.3.21 range; the vendor advisory GHSA-5vc5-wxxq-3fjx documents the fix, which replaces the suffix match with an exact path comparison.
- Remove Kestra from untrusted networks now. Because a single unauthenticated request yields root execution, restrict the Kestra API and UI to an internal management network or VPN immediately, and where an ingress must remain, block any request path whose final segment is
configsat the reverse proxy until the upgrade is complete. - Assume compromise and hunt thoroughly. Review all flows, triggers and namespaces for workflows no engineer created, especially any invoking
plugin-script-shellorplugin-script-python; inspect execution history for runs from unfamiliar sources, check worker containers for dropped binaries, cron entries and outbound connections, and examine logs for requests to paths ending inconfigs. - Rotate every secret Kestra can reach and harden long term. Because root inside the worker exposes the platform's entire credential store, rotate Kestra secrets, database credentials, cloud keys and service tokens used by flows; then disable script execution plugins that are not required, run workers with least privilege and network egress restrictions to blunt SSRF, and as a general rule implement authentication exemptions as exact-match allowlists rather than prefix or suffix tests.
Technical Details
CVE-2026-49869 chains several weaknesses that begin with one imprecise string comparison. Kestra OSS's AuthenticationFilter exempts the public configuration endpoint from Basic Auth using request.getPath().endsWith("/configs"), an incomplete input-matching rule (CWE-184) that, because it tests only the suffix, admits any API path whose last segment is configs — turning a narrow exemption into a general authentication bypass (CWE-287). With authentication removed, the attacker reaches the workflow API and creates and executes arbitrary flows. Kestra enables script execution plugins such as plugin-script-shell and plugin-script-python by default, so a workflow is a supported mechanism for running operating system commands (CWE-78), and those commands execute as root inside the Kestra worker container; workflows that fetch URLs additionally provide server-side request forgery (CWE-918) from the worker's network position. The CVSS vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H records the full combination — unauthenticated, network-reachable, low complexity, no interaction, changed scope, complete impact — which yields the 10.0 ceiling. The fix in 1.0.45 and 1.3.21 changes the exemption to an exact path match.
Frequently Asked Questions
Is CVE-2026-49869 being actively exploited?
Yes. CISA added CVE-2026-49869 to its Known Exploited Vulnerabilities catalog with a remediation due date of 5 September 2026, confirming exploitation in the wild. The vendor advisory publicly describes the flawed suffix match, and exploitation requires nothing more than an API request whose path ends in configs.
What products are affected by CVE-2026-49869?
Kestra OSS is affected in all versions before 1.0.45 and in the range 1.1.0 up to 1.3.21. Instances are especially exposed because Kestra ships with script execution plugins such as plugin-script-shell and plugin-script-python enabled by default, which is what turns the authentication bypass into remote code execution.
How do I fix CVE-2026-49869?
Upgrade Kestra to 1.0.45 or 1.3.21 or later, which replaces the suffix match with an exact path comparison, as described in advisory GHSA-5vc5-wxxq-3fjx. Immediately restrict the Kestra API to internal networks, audit all flows for workflows nobody created, and rotate every credential and secret the platform can reach.
How severe is CVE-2026-49869?
It is Critical, with the maximum CVSS 3.1 base score of 10.0. The vulnerability is unauthenticated, network-exploitable with low complexity, requires no user interaction, crosses a security scope boundary, and yields root-level remote code execution inside the Kestra worker container along with access to every secret the orchestrator holds; with confirmed KEV-listed exploitation and an expired remediation deadline, it is an emergency priority.
Need Help With Vulnerability Management?
Our security experts can help you prioritize and remediate vulnerabilities effectively.