Critical Pre-Auth RCE in Orkes Conductor Exploited to Compromise Workflow Orchestration

Security telemetry confirms active in-the-wild exploitation of CVE-2026-58138, a critical vulnerability carrying a CVSS score of 9.8 that allows unauthenticated remote code execution across Orkes Conductor workflow orchestrator deployments. Attackers exploit exposed API endpoints by submitting malicious inline workflow definitions containing JavaScript or Python expressions. Because the platform executes these tasks via GraalVM evaluators configured with unrestricted host access (`HostAccess.ALL`), the untrusted code breaks out of the scripting environment and executes arbitrary system-level commands with the privileges of the underlying Conductor host process. Workflow engines like Conductor orchestrate microservices, asynchronous data pipelines, and internal business logic across multi-cloud environments. Consequently, an unauthenticated breakout on this tier grants attackers an immediate foothold into core enterprise infrastructure. Rather than attacking isolated microservices, an adversary compromising the orchestrator inherits its execution context, service account credentials, and network connectivity. This allows unauthorized actors to intercept inter-service data streams, manipulate scheduled tasks, exfiltrate sensitive secrets, and pivot directly into internal control planes. This incident highlights a systemic risk across modern cloud-native architectures: the proliferation of polyglot expression evaluators and script runtimes within automated control layers. As teams build low-code orchestration and agentic AI execution pipelines, runtime engines frequently embed dynamic script execution to handle data transformations. When developer convenience overrides strict engine sandboxing—such as running evaluation engines without granular host boundaries—the boundary between data payloads and executable logic collapses entirely. The rapid weaponization of this vulnerability underscores how threat actors prioritize workflow tools as high-leverage entry points. DevOps and platform engineering teams running self-hosted Conductor instances must immediately upgrade deployments to version 3.30.2 or later. Beyond applying the patch, organizations should audit running instances to confirm they are completely isolated from the public internet behind authenticated API gateways or zero-trust network access (ZTNA) proxies. Ingress controls should enforce mandatory mutual TLS (mTLS) or strong identity validation on all workflow submission APIs. Finally, security teams should inspect historical access logs for unauthenticated POST requests directed at workflow evaluation endpoints to verify whether opportunistic threat actors established persistence prior to remediation.