Kestra: Unauthenticated Remote Code Execution via Authentication Bypass in `AuthenticationFilter`
Exploited in the wild, in CISA KEV since 2 Sep 2026 (due 5 Sep 2026), with 2 public exploits. No fixed version is recorded.
Kestra is an open-source, event-driven orchestration platform. Prior to 1.0.45 and 1.3.21, AuthenticationFilter in Kestra OSS uses 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. Because Kestra ships with script execution plugins (plugin-script-shell, plugin-script-python, etc.) enabled by default, this directly results in unauthenticated Remote Code Execution as root inside the Kestra worker container. This vulnerability is fixed in 1.0.45 and 1.3.21.
Briefing
Written from the sources below · deepseek-v4.1-flash
Kestra OSS before 1.0.45 and 1.3.21 lets AuthenticationFilter treat any path ending in "/configs" as public, allowing unauthenticated attackers to create and run workflows. Default script plugins then permit remote code execution as root in the worker container.
Why it mattersIt is in CISA KEV with confirmed exploitation, a public nuclei template, and EPSS of 20%, so unpatched internet-facing Kestra instances are at immediate risk.
ActionUpgrade to 1.0.45 or 1.3.21, or otherwise block API paths ending in /configs; hunt for workflow and shell execution indicators.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Kestra | OSS | ||
| kestra-io | <1.0.45, >=1.1.0 <1.3.21 |
Exploit evidence
2 public sources
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket