CVE-2026-49869: Kestra: Unauthenticated Remote Code Execution via Authentication Bypass in `AuthenticationFilter`
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.
Security readout for executives and security teams
Plain-English summary
A flaw in Kestra’s login protection lets an unauthenticated attacker reach normally protected API operations, create workflows, and run code. Default script plugins can turn this into root-level code execution inside the worker container, threatening workflow data, credentials, connected systems, and service availability.
Executive priority
Treat this as an emergency remediation and compromise-assessment issue. Prioritize Internet-accessible and business-critical Kestra deployments immediately, then all internally reachable instances. Because exploitation is documented and successful attacks can execute as root inside workers, upgrading alone should not replace retrospective log, container, credential, and downstream-system review.
Technical view
Kestra OSS AuthenticationFilter treats every request path ending in “/configs” as public instead of matching only the intended configuration endpoint. On affected releases, crafted API requests can therefore bypass Basic Auth. An attacker can create and execute workflows; default shell and Python script plugins enable code execution as root within the Kestra worker container.
Likely exposure
Affected Kestra OSS deployments are versions below 1.0.45 and versions from 1.1.0 through 1.3.20. Risk is greatest where Kestra APIs are reachable by untrusted networks. Internal deployments remain exposed to attackers with network access. The sources do not establish whether authentication mode, proxy rules, or plugin configuration reduce exposure in a specific deployment.
Exploitation context
CISA lists CVE-2026-49869 in the Known Exploited Vulnerabilities catalog, supporting active exploitation in the wild. Exploitation needs no credentials or user interaction and has low complexity. The supplied sources do not quantify campaign scale, identify threat actors, or describe confirmed victims.
Researcher notes
The core weakness is improper authentication caused by suffix-based path allowlisting, with command execution arising through legitimate workflow capabilities and default script plugins. The CVSS 3.1 score is 10.0 with network access, no privileges, no interaction, scope change, and high confidentiality, integrity, and availability impact. No exploit mechanics should be needed for defensive validation.
Mitigation direction
Upgrade the 1.0 branch to Kestra 1.0.45 or later.
Upgrade the 1.1–1.3 branch to Kestra 1.3.21 or later.
Restrict Kestra API access to trusted networks until upgrading is complete.
Review vendor guidance for any additional containment or incident-response recommendations.
Validation and detection
Inventory Kestra versions and flag releases within the documented affected ranges.
Confirm untrusted networks cannot reach Kestra APIs while remediation is pending.
Verify the deployed version is 1.0.45, 1.3.21, or an appropriate later release.
Review API and workflow audit records for unauthenticated creation or execution activity.
Inspect worker containers and connected credentials for evidence of compromise.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-184: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
CWE-918: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
Exploitation: activeAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.