Security / News explained
OpenJD's search-path flaw crosses the Deadline worker boundary
AWS's November disclosure concerns jobs running as the worker-agent user on customer-managed Linux fleets. The fixed library and worker releases predate the advisory.
AWS disclosed CVE-2026-126087 on November 10, 2026: an untrusted command-search path in OpenJD Sessions for Python can let a submitted job execute code as the Deadline Cloud worker-agent operating-system user. The problem affects customer-managed Linux fleets running vulnerable worker-agent versions. [1]
Service-managed fleets were remediated by AWS and need no customer action. Windows workers are not affected. Those scope distinctions are part of the advisory, rather than exceptions an operator has to infer from the product name. [1]
The job gets to influence a privileged choice
The project advisory explains that OpenJD Sessions used a bare command name when invoking sudo to switch to the queue's job user. Lookup occurred in an environment controlled by the job. A submitter with permission to create jobs could influence that lookup and cause job-supplied code to run under the worker-agent identity. [2]
According to the maintainers, that identity can access fleet-role and EC2 instance-identity credentials. On customer-managed hosts it can also reach other queues' session files and queue-role credentials. The advisory rates the issue High, with a CVSS score of 8.8. [2]
Our interpretation is that the identity transition is the important engineering failure. A job is supposed to run with the permissions assigned to its queue's job user. The mechanism that makes that transition must not let the submitted workload decide which program performs it.
This is also why an authenticated starting position does not make the issue harmless. Permission to submit work answers who may place a job in a queue. It does not automatically authorize that person to act as the agent hosting the work, or to inspect a neighboring queue's state.
The advisory names the worker-agent operating-system user as the execution identity. Its description should stay that precise. Assigning unrestricted root access to every affected deployment would add a claim about local privileges that these sources do not establish.
The fixed versions are older than the disclosure
AWS lists openjd-sessions versions before 0.11.0 and deadline-cloud-worker-agent versions before 0.33.0 as affected. Worker agent 0.33.0 includes the fixed OpenJD Sessions 0.11.0 library. [1]
The OpenJD 0.11.0 release notes are dated August 20, 2026. They describe resolving system commands from trusted directories instead of PATH and avoiding cached failed lookups. The November bulletin is therefore a later security disclosure concerning an existing fixed release. [3]
The worker-agent 0.33.0 release notes are dated August 21, 2026. They also identify compatibility-relevant changes, including a disk-usage metric changing from a fraction to a percentage. A worker update deserves normal operational review alongside its security priority. [4]
For a fleet owner, the useful observation is the version actually running on each applicable host. A dependency entry in a build file, a patched image waiting for deployment and an updated worker process describe different stages. An inventory should make those stages distinguishable rather than treating the desired version as proof of rollout.
Restricting submission buys time, not a repair
AWS says upgrading is the only fix and no configuration setting removes the issue. Until affected customer-managed fleets are upgraded, it recommends limiting job submission to trusted principals. [1]
The bulletin also advises reviewing CloudTrail for unexpected fleet-role and queue-role activity where affected versions ran on customer-managed fleets. [1]
A hypothetical shared Linux host makes the implication easier to see. If two queues rely on different job users, the hosting agent is part of what keeps their execution contexts distinct. A workload reaching that agent's identity changes the trust assumptions for both queues. This illustration is not a report that either queue or a customer's credentials were accessed.
In our view, temporary submission restrictions should have an explicit owner and an upgrade follow-up. Otherwise a useful short-term restriction can quietly become the permanent answer to a software flaw. Equally, applying the fixed version does not determine whether earlier activity needs investigation.
The practical consequence of the announcement is specific: identify affected customer-managed Linux workers, complete the applicable software update and assess the relevant activity. Keep service-managed remediation and the Windows exclusion visible. The failure occurred at a boundary between submitted work and its host; the response should preserve that distinction.
Sources + further reading
Source dates describe the original material. Publication above is the date this Zyel article went live.
- CVE-2026-126087: Untrusted search path in OpenJD Sessions and Deadline Cloud worker agentAWS Security · Checked Nov 11, 2026
- GHSA-g25v-j45m-7425: Job-controlled PATH and the worker-agent userAWS Deadline Cloud maintainers · Checked Nov 11, 2026
- OpenJD Sessions for Python 0.11.0 release notesOpen Job Description maintainers · Checked Nov 11, 2026
- Deadline Cloud worker agent 0.33.0 release notesAWS Deadline Cloud maintainers · Checked Nov 11, 2026
Reader discussion
What would you ask next?
Questions, useful corrections and thoughtful disagreement are welcome. Comments are reviewed before they appear.
No reader comments yet.