The 9.8 hiding in the workflow engine: Conductor is being hit and most teams do not know they run it

Fortinet put out an outbreak alert this week on a 9.8 that most security teams still cannot spell. CVE-2026-58138 sits in Orkes Conductor, the open-source workflow engine Netflix started and a lot of platform and AI teams now use to line up microservices and agents. SecurityWeek covered the in-the-wild use today. Empirical saw attacks in August. Fortinet said it blocked about 1,300 tries in a 24-hour window earlier this month, and thousands over the week.

What it actually is

Conductor lets you submit a workflow that includes little scripts. In vulnerable builds those scripts ran with far too much access to the machine underneath. The community server also ships with no login on the workflow API. Put those together and an unauthenticated caller on the network can hand the engine a hostile workflow and get operating-system commands as the Conductor process. The default container often runs as root.

The CVE posted on June 30. The complete fix shipped earlier, on June 3, in 3.30.2. The release notes talked about tightening GraalVM JavaScript. They did not scream "security." That is how a 9.8 spends a month off the patch list. Versions 3.30.0 and 3.30.1 are not enough. Do not stop there.

Orkes says Conductor runs in thousands of enterprises. Because the core is open source, plenty of installs never show up as "Conductor" in an asset list. They show up as a UI titled Conductor, an API on 8080, or a container an ML team stood up to orchestrate agents.

Why Friday is the day it got loud

A public proof of concept has been circulating since early August. That is when opportunistic scanning usually starts. Fortinet's numbers this week are the "it is no longer a lab demo" signal. This is not on CISA KEV as of this morning. Do not wait for the catalog. If the orchestrator is on the internet, treat it as an emergency change, then hunt.

What we would do this weekend

• Find it. Search for Conductor UI, conductoross images, Helm charts, and anything a data or AI team deployed for workflows. A clean Qualys or Tenable pass may say nothing. Empirical noted the plugin gap.
• Upgrade to 3.30.2 or later. Confirm the running image, not the repo tag someone meant to deploy.
• If you cannot move today, take the workflow API off the internet. Put authentication in front of it. Isolation is the lever until the build is current.
• Review recent workflow definitions and whether the Conductor process spawned shells it should never start. If the instance was exposed, assume more than a version bump is required.

Bottom line

The 9.8 you miss is the one that never made the meeting because nobody knew you ran it. Forensic Five reviews internet-facing applications for Canadian organizations, including the orchestration boxes the security team did not buy. From St. Albert, Alberta. If you have a Conductor UI on a public address, start there.