Home › Intelligence › Brief
VULNERABILITY BRIEF🟠 High Vulnerability

OS Command Injection in Kestra OSS (CVE‑2026‑49869) Enables Unauthenticated Workflow Execution

Kestra OSS, an open‑source workflow orchestration platform, contains a remote OS command‑injection flaw (CVE‑2026‑49869) that allows attackers to create and run arbitrary workflows without credentials. The vulnerability can be leveraged to compromise downstream systems or exfiltrate data. Organizations using Kestra must remediate the gap to retain audit‑ready control evidence.

LiveThreat™ Intelligence · 📅 October 07, 2026· 📰 nvd.nist.gov
🟠
Severity
High
VU
Type
Vulnerability
🎯
Confidence
High
🏢
Affected
1 sector(s)
✅
Actions
4 recommended
📰
Source
nvd.nist.gov

OS Command Injection in Kestra OSS (CVE‑2026‑49869) Enables Unauthenticated Workflow Execution

What It Is — Kestra OSS, an open‑source workflow orchestration engine, contains an OS command‑injection flaw (CVE‑2026‑49869). An attacker can craft a malicious workflow definition that the engine executes as a system command.

Exploitability — The vulnerability is remotely exploitable without authentication; proof‑of‑concept code is publicly available. CVSS rating is reported as 9.1 (High).

Affected Products — Kestra OSS (all versions prior to the vendor’s security release).

Why It Matters for Trust & Control Assurance

  • Demonstrates a gap in the execution‑control objective: without proper safeguards, any user (or attacker) can run arbitrary OS commands.
  • Continuous control‑mapping lets you tie this gap to a single VCF control objective, which in turn satisfies multiple frameworks (e.g., NIST CSF 2.0).
  • Capturing runtime logs and evidence of workflow validation provides a defensible audit trail that buyers increasingly demand.

Recommended Actions

  • Apply the vendor‑released patch or upgrade to the latest Kestra OSS version.
  • Enforce strict validation of workflow definitions and restrict who can submit them.
  • Deploy runtime monitoring and immutable logging of workflow execution to capture evidence of control enforcement.
  • Map the “execution‑control” objective to your framework of record to demonstrate remediation.

Source: CISA KEV – CVE‑2026‑49869

📰 Original Source
https://nvd.nist.gov/vuln/detail/CVE-2026-49869 ↗

This LiveThreat Intelligence Brief is an independent analysis. Read the original reporting at the link above.

From the Verisq platform · Trust Operations

Misconfigurations are control gaps in disguise.

Verisq AI Trust Operations turns findings like this into mapped controls with continuous evidence, keeping your audit readiness current instead of point-in-time.

Map your controls with Verisq AI Trust Operations →