Quick answer
Yes. CVE-2026-49869 in Kestra Kestra OSS is being exploited by attackers: CISA added it to its Known Exploited Vulnerabilities catalogue on 2 September 2026. If you run Kestra OSS, apply the vendor's fix now and check for signs of compromise.
What is CVE-2026-49869?
Kestra OSS OS Command Injection Vulnerability. Kestra OSS contains an OS command injection vulnerability that could allow an unauthenticated remote attacker to create and execute arbitrary workflows without credentials.
Description from the CISA Known Exploited Vulnerabilities catalogue.
What kind of flaw is it?
Input reaches an operating system command, so an attacker can run their own commands on the device.
Other exploited os command injectionThe system does not properly check who is logging in, so an attacker can get in without valid credentials.
Other exploited improper authenticationThe server can be made to send requests on the attacker's behalf, often reaching internal systems or cloud credentials.
Other exploited server-side request forgery (ssrf) How it worksWhy it matters
Source code platforms, build servers and collaboration tools hold code, secrets and credentials. Exploiting them can lead to supply chain attacks on everyone who uses your software.
Higher than 82% of all scored vulnerabilities.
Am I affected? How to check | What to do now |
|---|---|
1Confirm whether you self-host the affected tool. | 1Apply the vendor fix. |
2Check versions against the advisory and whether the instance is internet-facing. | 2Rotate tokens and secrets stored in the platform if exposure is possible. |
3Review audit logs for new tokens, accounts or changes to pipelines. | 3Restrict access to internal networks or SSO-protected access. |
Am I affected? How to check
- 1Confirm whether you self-host the affected tool.
- 2Check versions against the advisory and whether the instance is internet-facing.
- 3Review audit logs for new tokens, accounts or changes to pipelines.
What to do now
- 1Apply the vendor fix.
- 2Rotate tokens and secrets stored in the platform if exposure is possible.
- 3Restrict access to internal networks or SSO-protected access.
CISA required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk guidance and CISA’s “Forensics Triage Requirements”. 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.
How fast to patch
Under the Essential Eight, patches for internet-facing services should be applied within 48 hours when a working exploit exists, and higher maturity levels apply the same 48-hour target to applications such as browsers and office software. A vulnerability in this catalogue has, by definition, been exploited in the wild, so treat it as the 48-hour case.
Common questions
Is CVE-2026-49869 being exploited?
Yes. It is listed in CISA's Known Exploited Vulnerabilities catalogue, which only includes vulnerabilities with confirmed exploitation in the wild. It was added on 2 September 2026.
How do I fix CVE-2026-49869?
Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk guidance and CISA’s “Forensics Triage Requirements”. 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. Check the vendor advisory for fixed versions, and if the system was exposed while unpatched, investigate it for signs of compromise.
Is my Kestra Kestra OSS affected?
Check your installed version against the vendor advisory linked on this page. If the affected component is reachable from the internet and unpatched, assume it is at risk and act immediately.