Skip to content
StrikeCyberStrikeCyber
Threat Radar · Actively exploited

Kestra Kestra OSS (CVE-2026-49869)

Exploited in the wild Added September 2, 2026 EPSS 2.1%Dev tools

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 September 2, 2026. If you run Kestra OSS, apply the vendor's fix now and check for signs of compromise.

ConfirmedExploited in the wild
Not knownRansomware use
2.1%EPSS · top 18%
September 2,Added to CISA KEV

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?

OS command injectionCWE-78

Input reaches an operating system command, so an attacker can run their own commands on the device.

Other exploited os command injection
Improper authenticationCWE-287

The system does not properly check who is logging in, so an attacker can get in without valid credentials.

Other exploited improper authentication
Server-side request forgery (SSRF)CWE-918

The 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 works

Why 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.

Likelihood of exploitation activity in the next 30 days (EPSS)2.1%

Higher than 82% of all scored vulnerabilities.

Am I affected? How to check

  1. 1Confirm whether you self-host the affected tool.
  2. 2Check versions against the advisory and whether the instance is internet-facing.
  3. 3Review audit logs for new tokens, accounts or changes to pipelines.

What to do now

  1. 1Apply the vendor fix.
  2. 2Rotate tokens and secrets stored in the platform if exposure is possible.
  3. 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.

Deadline and priority

CISA requires US federal civilian agencies to remediate catalogued vulnerabilities by the listed due date under Binding Operational Directive 22-01 (September 5, 2026 for this one), and strongly urges every organization to prioritize them the same way.

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 September 2, 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.

Sources

(877) 657-8496