# CVE-2026-114085: Trigger.dev through 4.7.6 Missing Authentication in Supervisor Workload API


- **Severity:** High 8.8 (`CVSS:4.0/AV:A/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:L/SC:H/SI:H/SA:L`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 21 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** GHSA-jc26-22qp-cgqj, GHSA-mjhg-96gj-78w9

## What is CVE-2026-114085?

CVE-2026-114085 is a high-severity vulnerability in triggerdotdev trigger.dev, published on 21 Oct 2026. 

### Official description

Trigger.dev through 4.7.6 contains a missing authentication vulnerability in the supervisor workload server that allows workloads to manipulate runs belonging to other deployments without ownership verification. Attackers with network access and a valid run/snapshot pair can call the attempts/start endpoint to obtain resolved environment variables and run JWTs, or start, complete, and suspend other tenants' runs.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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


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

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

## Is CVE-2026-114085 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-114085 is a high-severity vulnerability in triggerdotdev trigger.dev, published on 21 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-114085 in the wild and no public exploit code.

Affected product: triggerdotdev trigger.dev. 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-114085/ (Markdown: https://insights.sbomify.com/CVE-2026-114085/index.md)
```

## Sources

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

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