CVE-2026-49869

Kestra OSS command injection, confirmed exploited in the wild.

Kestra OSS contains an OS command injection vulnerability that could allow an unauthenticated remote attacker to create and execute arbitrary workflows without credentials.

Check your domain free How we watch for this

2.1%chance of exploitation in the next 30 days (EPSS), 81st percentile

2 Sepadded to CISA's Known Exploited Vulnerabilities list, 2026

5 Sepfederal remediation deadline, already passed

Passedpast the deadline: patch now

CISA's name for it	Kestra OSS OS Command Injection Vulnerability
Vendor and product	Kestra · Kestra OSS
Type	command injection · CWE-78, CWE-184, CWE-287, CWE-918
Exploited	Confirmed by CISA listed 2 September 2026
Likelihood	more likely to be exploited than most
Deadline	5 September 2026 · already passed
Used in ransomware	Not reported
Advisories	github.com ↗ · www.cisa.gov ↗ · www.cisa.gov ↗ · nvd.nist.gov ↗

What to do

Three steps, in this order

Step 1

Apply the vendor fix; command injection on an exposed device is used within days of disclosure.

Step 2

Restrict the management interface to a trusted network until the fix is in.

Step 3

Review the device's logs and configuration for changes you did not make.

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.

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.

Is it on your estate?

Know before someone else finds it

Threat Landscape Monitoring fingerprints the software your internet-facing hosts disclose and matches it, every day, against this list and the exploitation scores. When a new entry touches something you run, you are told once, with the host and the fix. The free plan covers one domain.

Start free with one domain Run the free domain check

Questions

CVE-2026-49869 in short

Is CVE-2026-49869 being exploited?

Yes. CISA added CVE-2026-49869 to its Known Exploited Vulnerabilities catalogue on 2 September 2026, which it does only on evidence of exploitation in the wild.

What is the CISA deadline for CVE-2026-49869?

US federal agencies must remediate it by 5 September 2026. Everyone else should treat that date as the latest safe point to patch an internet-facing system.

How likely is CVE-2026-49869 to be exploited in the next 30 days?

FIRST's Exploit Prediction Scoring System gives it 2.1%, the 81st percentile of every CVE it scores.

How do I fix CVE-2026-49869?

Apply the vendor fix; command injection on an exposed device is used within days of disclosure. Restrict the management interface to a trusted network until the fix is in. Review the device's logs and configuration for changes you did not make.

Sources: CISA Known Exploited Vulnerabilities catalogue (released 10 November 2026) and FIRST EPSS. Page compiled automatically by SAK T.L.M, the threat-intelligence tool of SAK T.E.C, on 13 November 2026.