IPS Signature Sep 19, 2026

GajIPS - IPS Signature Update — GS EXPLOIT: Orkes Conductor unauthenticated workflow RCE, CVE-2026-58138

Severity: CRITICAL · Priority: P1 — active exploitation, escalate on hit

These rules raise an alert when an attacker attempts to exploit a critical flaw in Orkes Conductor, an open-source workflow-orchestration platform used to run automated business and data pipelines. Conductor lets a workflow include small script expressions, and in affected versions it runs those scripts with unrestricted access to the underlying system — so an attacker who submits a workflow containing a malicious script can break out and run operating-system commands on the server. Because the community workflow interface has no authentication by default, no login is required: simply submitting the crafted workflow to an exposed Conductor server is enough. The flaw can be exploited through either of the platform's two supported scripting languages, and these rules cover both, watching the workflow registration and start interfaces for the specific system-command techniques used in each.

A hit indicates an attempt to exploit this flaw against one of your servers. The flaw is rated critical (9.8), affects Conductor versions 3.21.21 up to 3.30.2, and is under active exploitation, with public exploit code available and security vendors reporting large numbers of blocked attempts. Treat an alert as a serious exploitation attempt: confirm whether the targeted host runs Orkes Conductor and whether it is on version 3.30.2 or later; if it is unpatched and its workflow interface is reachable, assume the attempt may have succeeded and escalate to incident response. Because a successful attack runs commands with the Conductor process's privileges — and Conductor often holds credentials for the systems it orchestrates — treat any secrets and service credentials reachable from that host as potentially exposed and rotate them, and hunt for unexpected commands, processes, or outbound connections from the server. Upgrading to Conductor 3.30.2 or later, and not exposing the workflow interface to untrusted networks, are the definitive fixes.

See the latest threat intelligence