# CVE-2026-114069: Trigger.dev before 4.6.0 Root Secret Disclosure via envvars API Endpoint


- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 21 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-4gjx-f5hj-678x, GHSA-8jgj-f949-3f8m

## What is CVE-2026-114069?

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

### Official description

Trigger.dev before 4.6.0 contains an improper authorization vulnerability in the GET /api/v1/projects/:projectRef/envvars endpoint, which returns the environment's root API key as TRIGGER_SECRET_KEY for staging, production, and preview environments. Attackers holding a restricted read:envvars key can obtain the root secret and plaintext secrets, then trigger tasks and mint admin public JWTs.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2026-114069 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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