Unauthenticated RCE in Orkes Conductor CVE-2026-58138 Exploited Since August

The vulnerability stems from Conductor's GraalVM context configured with HostAccess.ALL, allowing user-supplied JavaScript or Python in INLINE, LAMBDA, DO_WHILE, and SWITCH tasks to escape the sandbox and execute OS commands as root. No authentication is enforced by default on the workflow API, enabling a single unauthenticated POST to register and trigger hostile tasks. The flaw was patched in version 3.30.2 in June, yet PoC code surfaced publicly in early August and active exploitation followed within weeks.

Empirical Security documented in-the-wild attacks starting August 21 while Fortinet issued an outbreak alert after blocking roughly 1,300 probes in two days. Procurement records and deployment patterns show Conductor instances frequently exposed directly to the internet for microservice orchestration, including AI agent workflows. This matches a recurring pattern where open-source workflow engines ship with permissive defaults that persist in production despite available patches.

Organizations must isolate Conductor endpoints behind strict firewalls, enforce authentication immediately, and scan for unauthorized workflow submissions. Unpatched instances remain high-value targets for initial access brokers who chain the RCE into broader network footholds. Monitoring for anomalous Java or Python expression evaluation in logs provides the clearest detection signal.

Next indicators will appear in public exploit frameworks and additional vendor telemetry within 30 days if adoption of 3.30.2 remains low.