Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach exposed workflow API
-
DeliverySubmit inline workflow with malicious script
-
ExploitGraalVM evaluates JS/Python unsandboxed
-
ExecutionJava reflection spawns subprocess
-
ImpactExecute arbitrary OS commands on host
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Code injection prevention, sandbox exec
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires that the target Conductor (3.21.21 through 3.30.1) expose its workflow API to the attacker and that its embedded GraalVM JavaScript/Python evaluators be configured unsandboxed with HostAccess.ALL or allowAllAccess(true) - that misconfiguration is the decisive prerequisite. Given that, an attacker needs only to submit an inline workflow definition using INLINE, LAMBDA, DO_WHILE, or SWITCH task types carrying a malicious script expression, with no credentials (PR:N), no user interaction (UI:N), and network access only. Limiting factors: instances that restrict GraalVM host access, that do not expose the workflow definition endpoint to untrusted networks, or that have upgraded to 3.30.2+ are not exploitable; the dependence on the unsandboxed evaluator configuration means default-hardened deployments may be safe. |
| Impact | All available signals point to a genuine high priority rather than a paper-tiger CVSS. The CVSS 4.0 base of 9.3 (AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H) describes network-reachable, pre-authentication, no-interaction RCE with full confidentiality/integrity/availability loss - the worst practical profile. The one important nuance is the description's stated prerequisite: exploitation depends on the GraalVM evaluators being configured unsandboxed (HostAccess.ALL / allowAllAccess(true)), which is a deployment/configuration condition the vendor's CVSS does not reflect as added complexity; in my independent view this warrants AC:H/AT:P. No EPSS score was supplied, and the input contains no KEV flag and no explicit POC flag, so this is not confirmed actively exploited and no public exploit is identified - the risk is driven by ease of exploitation and exposure, not by observed in-the-wild activity. Given that Conductor APIs are often network-exposed in microservices environments, instances running the vulnerable config should be treated as critical and patched immediately. |
| Exploit ScenarioDerived | An attacker who can reach a Conductor instance's workflow API submits a crafted inline workflow whose INLINE or LAMBDA task contains a JavaScript or Python expression that uses Java reflection to instantiate a process and run shell commands. Because evaluation happens pre-authentication on an unsandboxed GraalVM context, the command executes with the privileges of the Conductor JVM, giving the attacker server-side code execution. No public exploit code is identified, but the technique is well documented in the VulnCheck advisory. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jun 30, 2026
Unauthenticated remote code execution in Orkes Conductor (conductor-oss) versions 3.21.21 through 3.30.1 lets remote attackers run arbitrary OS commands by POSTing inline workflow definitions to the workflow API before any authentication check. The flaw stems from GraalVM script evaluators left in an unsandboxed state (HostAccess.ALL / allowAllAccess(true)), allowing JavaScript or Python expressions in INLINE, LAMBDA, DO_WHILE, and SWITCH tasks to reach Java reflection and subprocess APIs. Reported by VulnCheck; no public exploit identified at time of analysis, though a detailed vendor/researcher advisory exists.
RemediationAI
Vendor-released patch: upgrade to Conductor v3.30.2 or later, which contains the hardening commits (87a7d96 and c691e35) referenced in the release at https://github.com/conductor-oss/conductor/releases/tag/v3.30.2. Where immediate upgrade is not possible, the most effective compensating control targets the root cause: reconfigure the GraalVM script evaluators away from HostAccess.ALL / allowAllAccess(true) to a restricted host-access policy so guest scripts cannot reach Java host objects, accepting that legitimate workflows relying on broad host interop may break and need rework. As additional measures, disable or restrict the INLINE, LAMBDA, DO_WHILE, and SWITCH script-evaluating task types if unused, and place the workflow API behind authentication and network controls so the unauthenticated definition-submission endpoint is not reachable from untrusted networks - noting this reduces exposure but does not remove the underlying injection. Consult the VulnCheck advisory (https://www.vulncheck.com/advisories/orkes-conductor-unauthenticated-rce-via-graalvm-script-evaluators) for specifics before applying config changes.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Conductor is an open-source microservices workflow-orchestration engine (originating from Netflix Conductor, maintained as conductor-oss/Orkes Conductor) that lets users define workflows whose tasks can embed inline script expressions. To evaluate those expressions it embeds GraalVM polyglot script engines for JavaScript and Python. The root cause is CWE-94 (Improper Control of Generation of Code / code injection): when the GraalVM context is created with HostAccess.ALL or allowAllAccess(true), guest scripts are granted full host-Java interop, so attacker-supplied script bodies can use Java reflection (e.g., java.lang.Runtime/ProcessBuilder) or direct subprocess calls to escape the intended sandbox and execute on the host JVM. The affected component per NVD CPE is cpe:2.3:a:conductor-oss:conductor (all versions in the stated range up to the fix).
Know when Conductor gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Network pre-auth, no interaction (PR:N/UI:N) yielding full host RCE, but exploitation depends on a non-default unsandboxed GraalVM config, so AC:H.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
DescriptionCVE.org
Orkes Conductor 3.21.21 before 3.30.2 contains an unauthenticated remote code execution vulnerability that allows remote attackers to execute arbitrary OS commands by submitting inline workflow definitions containing malicious JavaScript or Python expressions to the workflow API endpoint prior to authentication. Attackers can exploit unsandboxed GraalVM evaluators configured with HostAccess.ALL or allowAllAccess(true) through INLINE, LAMBDA, DO_WHILE, and SWITCH task types to invoke arbitrary system commands via Java reflection or direct subprocess calls.
Articles & Coverage 3
Executive ViewAI
Orkes Conductor (versions 3.21.21-3.30.1) contains a critical unauthenticated remote code execution vulnerability allowing remote attackers to execute arbitrary OS commands on affected systems without authentication. Organizations running this workflow orchestration platform face complete infrastructure compromise, including unauthorized access to data, lateral movement, and persistence establishment. Immediate patching is required.
Apply vendor patch. Until patching is complete, implement network segmentation to restrict unauthenticated access to the Conductor workflow API endpoint; require VPN or firewall allowlist for all API connections.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Code injection occurs when an application accepts user input and passes it directly into a language interpreter or evaluator without proper sanitization.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
Netflix Titus uses Java Bean Validation (JSR 380) custom constraint validators. Rated critical severity (CVSS 9.8), this
Server-side request forgery in Conductor OSS through 3.33.0-rc10 lets remote attackers influence the kafka_request.bootS
Server-side request forgery in Conductor OSS through 3.32.5 allows unauthenticated remote attackers to force the server
Server-side request forgery in conductor-oss Conductor through 3.33.0-rc10 allows unauthenticated remote attackers to in
Server-side request forgery in conductor-oss Conductor 3.31.2 allows an authenticated low-privileged user to force the s
Server-side request forgery (CWE-918) in the MCP Service of conductor-oss Conductor 3.22.0 lets an authenticated low-pri
EUVD-2026-40377
GHSA-7x5q-8f6h-rjrc
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB
VulDB