# CVE-2026-126087: 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


- **Severity:** Critical 9.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:L`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 10 Nov 2026
- **Updated:** 10 Nov 2026

## What is CVE-2026-126087?

CVE-2026-126087 is a critical vulnerability in AWS deadline-cloud-worker-agent, published on 10 Nov 2026. 

### Official description

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.

Weakness: CWE-426 (Untrusted Search Path)

## Which versions are affected by CVE-2026-126087?


## How do I fix CVE-2026-126087?

No fix has been published for CVE-2026-126087 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-126087 being exploited?

There is no known exploitation of CVE-2026-126087 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-126087 and fix it if it is affected.

What it is: CVE-2026-126087 is a critical vulnerability in AWS deadline-cloud-worker-agent, published on 10 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-126087 in the wild and no public exploit code.

Affected product: AWS deadline-cloud-worker-agent. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-126087/ (Markdown: https://insights.sbomify.com/CVE-2026-126087/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-126087
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-126087
- OSV: https://osv.dev/vulnerability/CVE-2026-126087

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-126087/
Summaries are generated and may contain mistakes; the official description above is the record.