CVE-2026-126087AWS openjd-sessions untrusted search path
CVE-2026-126087 is a untrusted search path in AWS openjd-sessions, rated critical (9.4 on CVSS 4.0).
Why this priority: Critical severity, with no exploitation signal yet.
Published · Updated · NVD status: Received
What it is
The software looks for files or programs in places an attacker can write to.
How it is reached
An attacker can exploit it over the network, with an ordinary user account, and nobody has to click anything.
What an attacker gains
A successful attack can read the data it protects, change data or behaviour and take it offline. In practice, this kind of flaw lets an attacker run their code inside your build or your running service. The damage can spread past the vulnerable component into others.
Is it being exploited?
There is no public report of exploitation yet.
What to do
- Upgrade AWS openjd-sessions to 0.11.0 or later. Other affected products have their own fixed versions on this page.
- Until it is patched, review who holds accounts that can reach it.
Description from NVD
Untrusted search path in the cross-user process launcher in Open Job Description (OpenJD) Sessions for Python before 0.11.0, as used in the AWS Deadline Cloud worker agent before 0.33.0, on Linux might allow an authenticated remote user with permission to submit jobs to a queue to execute arbitrary code as the worker agent OS user and obtain the AWS credentials held by the worker agent via a crafted job that modifies the PATH environment variable.
To remediate this issue, users of customer-managed fleets should upgrade the Deadline Cloud worker agent to version 0.33.0 or later, which includes OpenJD Sessions 0.11.0. Service-managed fleets were remediated service-side.
What this means for your architecture.
A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.
Components it touches
- Build pipelines, dependencies and plugins. The flaw sits between third-party code and your build or runtime.
- Update channels. The flaw sits between third-party code and your build or runtime.
Trust boundaries in play
- Authenticated network access. An account is needed, so exposure follows who can sign in: customers, partners or staff.
- Isolation between components. The impact crosses out of the vulnerable component into others it should be isolated from.
- Between third-party code and your build or runtime. An attacker who crosses it can run their code inside your build or your running service.
Questions to answer about your own systems
- Where does AWS openjd-sessions run in your systems, and at which version?
- Which of those instances can be reached from the internet or partner networks?
- What can it reach once compromised: which data stores, secrets and services?
Sources
- CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
- Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
- Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
- Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.