Workflow engines sit in an odd place. They get stood up by a platform team, wired into half the estate, and then left alone because they work. That is the profile of CVE-2026-58138, a 9.8-rated flaw in Orkes Conductor, the orchestration layer many teams use to connect services, databases and, increasingly, AI agents.
How it works
Conductor lets you define workflows with embedded JavaScript or Python expressions. Per the NVD description quoted by eSecurityPlanet, the GraalVM evaluators can be made to escape their intended restrictions and call operating system commands through the INLINE, LAMBDA, DO_WHILE and SWITCH task types. The commands run as the Conductor process. Nobody needs credentials; they need network reach to the workflow API.
What defenders are seeing
Fortinet's outbreak alert reports 6,696 blocked attempts across seven days and 1,290 in a single day, a 132 per cent jump in daily activity, plus a working public exploit aimed at v3.23.0. The Hacker News also covers the exploitation, and the reporting notes a 21 September warning from SK-CERT. Blocked attempts are only the ones a single vendor could see; they say nothing about the unprotected hosts.
The real question is exposure
A patch exists in 3.30.2, and 3.30.0 and 3.30.1 are still vulnerable, so "we're on a 3.30 build" is not an answer. The harder job is finding every Conductor instance. Some will be in a dev cluster somebody exposed for a demo, some inside a vendor product that bundles it. The workflow API being reachable from the internet is the condition that turns a bad bug into an incident.
- Search your asset inventory and cloud accounts for Conductor, including copies embedded in other products.
- Upgrade to 3.30.2 or later; treat 3.30.x below that as unpatched.
- Take /api/metadata/workflow and /api/workflow off the public internet, or put authentication in front of them.
- Review stored workflow definitions for scripts nobody on the team wrote.
- Watch the Conductor Java process for child processes and odd outbound connections; rotate any secrets the host could read if you find either.
If you would like help with an internet-exposure sweep or reviewing how your orchestration tooling is secured, email sales@halfteck.com.