# CVE-2026-114092: Trigger.dev before 4.5.0 Missing Authentication in Dashboard Run Replay Action


- **Severity:** High 8.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 21 Oct 2026
- **Updated:** 22 Oct 2026
- **Also known as:** GHSA-4ggh-4c33-wrjj

## What is CVE-2026-114092?

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

### Official description

Trigger.dev before 4.5.0 performs no authentication or organization check in the action handler of the dashboard run replay route (resources.taskruns.$runParam.replay) and looks up the run by friendlyId alone. A remote attacker who knows a victim's run friendlyId can replay it into an environment of their choosing, exposing the victim's task payload or running the task again with the victim's secrets.

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

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


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

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

## Is CVE-2026-114092 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-114092 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-114092 is a high-severity vulnerability in triggerdotdev trigger.dev, published on 21 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-114092 exists.

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-114092/ (Markdown: https://insights.sbomify.com/CVE-2026-114092/index.md)
```

## Sources

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

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