Kestra · Kestra OSS · CWE-78 · CWE-184 · CWE-287 · CWE-918 · published 2026-06-26
CVE-2026-49869Kestra OSS OS Command Injection Vulnerability
Patch today Known exploited (CISA KEV) and CISA requires forensic triage: patch and check for compromise.
CVE-2026-49869 is actively exploited in the wild: CISA added it to the Known Exploited Vulnerabilities catalog on 2026-09-02. EPSS estimates a 2.1% chance of exploitation in the next 30 days, higher than 82% of all CVEs. This Kestra OSS vulnerability: CVSS 10.0 (v3.1), attacks can be automated, a successful attack gives total control of the component. CISA’s required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines. US federal agencies must remediate by 2026-09-05. Patch today.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
CISA required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines. (federal due date 2026-09-05)
Patch events
Other softwareKestra OSS
OSS OS Command InjectionCVE-2026-49869
Why: Known exploited (CISA KEV) and CISA requires forensic triage: patch and check for compromise.
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | Yes, added 2026-09-02 | CISA KEV |
| Ransomware use | Unknown | CISA KEV |
| EPSS (30-day exploitation probability) | 2.1% (82th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 10.0 (v3.1)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H | CNA / CISA ADP |
| SSVC exploitation | active | CISA Vulnrichment |
| SSVC automatable | Yes | CISA Vulnrichment |
| SSVC technical impact | total | CISA Vulnrichment |
Weakness: CWE-78: Improper Neutralization of Special Elements used in an OS Command · CWE-184: Incomplete List of Disallowed Inputs · CWE-287: Improper Authentication · CWE-918: Server-Side Request Forgery
More from this vendor: all Kestra vulnerabilities · recent KEV additions
Affected versions (from the CVE record)#
- kestra-io kestra
< 1.0.45(affected)>= 1.1.0, < 1.3.21(affected)
Description (from the CVE record)#
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.
Quoted from the CVE Program record.