Attackers Are Hammering Orkes Conductor Servers With No-Login Attacks That Run OS Commands

Attackers are breaking into Orkes Conductor servers without a login and running commands on the host.

The bug is CVE-2026-58138, scored 9.8, SecurityWeek reported. Fortinet blocked about 1,290 attempts in a 24-hour window around 8 and 9 September, and nearly 7,000 between 2 and 9 September. The flaw is not on CISA's Known Exploited Vulnerabilities list. Nobody has said Orkes Cloud itself was breached.

Orkes Conductor is an open-source framework for orchestrating microservices, workflows, and AI agents. Attackers submit crafted inline workflow definitions to the workflow API. They embed malicious JavaScript or Python in INLINE, LAMBDA, DO_WHILE, and SWITCH tasks.

The root cause is a GraalVM evaluator configured with HostAccess.ALL or allowAllAccess(true). That setting disables the sandbox, so attacker code can reflect into the Java runtime or spawn OS commands as the Conductor process. The Conductor process often runs with root privileges, though that is not true of every deployment.

The open-source server enforces no authentication by default and leaves the workflow API open. Empirical Security said a single unauthenticated POST can register and start a hostile workflow.

The flaw affects 3.21.21 before 3.30.2 and was patched in Conductor 3.30.2 in June 2026. Proof of concept code appeared in early August. Empirical saw in-the-wild exploitation on 21 August.

Attack traffic was noted from Germany, Hong Kong, Indonesia, the UAE, and India, about 132 percent higher daily activity in that early-September window. The same class of unauthenticated orchestration RCE showed up recently in Kestra's auth-bypass RCE.

Some offers on this page may be paid placements or contain affiliate links.