← gociux.comall exploited CVEs

Exploited vulnerability · CISA KEV

Is CVE-2026-49869 exploited? Yes: in CISA KEV since 2 Sep 2026

Gociux · Kestra OSS · data: CISA KEV, CVE record, FIRST EPSS

Yes. CVE-2026-49869, Kestra OSS OS Command Injection Vulnerability, is being exploited in the wild. CISA added it to its Known Exploited Vulnerabilities catalog on 2 Sep 2026, 68 days after it was published. It affects Kestra OSS. If you run it, CISA's required action is: 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.

exploitedYesCISA KEV · 2 Sep 2026
ransomwareNot knownno confirmed use
EPSSbelow top 10%lower predicted activity right now (it is still confirmed exploited)
severity10CVSS 3.1 · critical
US federal due5 Sep 2026BOD 22-01 deadline

What it is

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

VendorKestra (1 exploited CVE in KEV)
ProductKestra OSS
VulnerabilityKestra OSS OS Command Injection Vulnerability
WeaknessCWE-78, CWE-184, CWE-287, CWE-918
Published26 Jun 2026
Added to KEV2 Sep 2026
Reported by (CNA)GitHub_M

What to do

  1. Check whether you run it. Look for Kestra OSS in your asset inventory, including appliances and cloud images. Stack check lists every exploited Kestra CVE at once.
  2. Apply the fix. 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.
  3. If you can't patch today, take the affected service off the internet or restrict who can reach it, and check its logs for signs of compromise since 26 Jun 2026.
  4. Get told next time. Email alerts when CISA adds a CVE for Kestra.

References

Questions

Is CVE-2026-49869 being exploited?

Yes. CISA added CVE-2026-49869 to the Known Exploited Vulnerabilities catalog on 2 Sep 2026, which means there is reliable evidence of exploitation in the wild.

Is CVE-2026-49869 used in ransomware attacks?

CISA does not list known ransomware use for it. That can change, and exploitation alone is reason to fix it first.

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 (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. Check Kestra's advisory for the fixed versions, and if you can't patch quickly, restrict access to the affected Kestra OSS and watch it for signs of compromise.

Sources: CISA KEV (exploitation, ransomware use, required action, due date), the CVE record (publication date, CVSS, CNA), NVD and FIRST EPSS (live score). More: all KEV additions in September 2026 · act-now radar.

Running Kestra in a regulated environment?

We check exposure across your estate, patch or mitigate with your team, and set up detection for what attackers do after exploiting it.

Get in touch →