Orkes Conductor (versions prior to 3.30.2)
Conductor is an open-source enterprise framework used by organisations to coordinate microservices, automated workflows, and AI agents — think of it as the traffic controller that tells different software components what to do and when.
Root Cause
Conductor's INLINE task type evaluates user-supplied JavaScript or Python expressions. The evaluator runs inside a GraalVM context — a runtime environment for code — configured with all host access enabled. That setting disables the sandbox (the protective barrier that normally stops code from touching the underlying system). Attacker-supplied code escapes directly into the Java runtime and executes OS commands. The server enforces no authentication by default, so the API endpoint is entirely open.
Attack Vector
An attacker sends a single unauthenticated HTTP POST request to Conductor's workflow API. The request registers a new workflow containing a hostile INLINE task with embedded malicious code. Conductor evaluates the expression, the sandbox check fails silently, and the code executes as the Conductor process — which commonly runs with root privileges. No credentials, no phishing, no foothold required. Proof-of-concept code has been public since early August, and Fortinet recorded roughly 1,300 exploitation attempts in a single 48-hour window in September, per SecurityWeek.
Detection Notes
Look for unexpected POST requests to /api/workflow endpoints in your web server logs, particularly from external IPs. Monitor for unusual process execution spawned by the Conductor service — commands like curl, wget, or shell invocations are red flags. Review running workflows for any INLINE tasks you did not create.
Recommended Actions
- Upgrade to Orkes Conductor version 3.30.2 or later immediately.
- Place Conductor behind a firewall and block all external access to its workflow API endpoints.
- Enable monitoring for suspicious workflow submissions and review any system running a vulnerable version for signs of prior compromise.