# Trigger.dev: Cross-environment deployment cancel

Advisory record · `GHSA-4672-hwv6-gq62`

- **Identifiers:** `GHSA-4672-hwv6-gq62` · `CVE-2026-114079`
- **State:** Confirmed
- **Severity:** CVSS 5.3 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-639](https://cwe.mitre.org/data/definitions/639.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 2 Oct 2026
- **Updated:** 21 Oct 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 2 Oct 2026, 22:42 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `trigger.dev` (npm): affected `<4.5.6`; fixed in `4.5.6`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Trigger.dev versions before 4.5.6 (npm package trigger.dev) let a secret API key for one environment of a project cancel in-progress deployments in other environments of the same project, including production, even though reading those deployments is correctly restricted. An attacker needs a valid key for any environment in that project, such as a development or preview key. Upgrade to version 4.5.6 or later, which is the fixed version listed.

Written 31 Oct 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 5.3 Medium, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N`, from CNA (VulnCheck)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0030, the 23rd percentile, on 15 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 13:33 UTC: First seen by agentprime
- 31 Oct 2026, 13:33 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-4672-hwv6-gq62)

## Sources

- [GitHub Advisory Database: GHSA-4672-hwv6-gq62](https://github.com/advisories/GHSA-4672-hwv6-gq62)
- [OSV: GHSA-4672-hwv6-gq62](https://osv.dev/vulnerability/GHSA-4672-hwv6-gq62)
- <https://github.com/triggerdotdev/trigger.dev/security/advisories/GHSA-4672-hwv6-gq62>
- <https://github.com/triggerdotdev/trigger.dev/pull/4316>
- <https://github.com/triggerdotdev/trigger.dev/commit/6997aeb05e27d2db47f9eda01fdc8a17c81a1ae0>
- <https://github.com/triggerdotdev/trigger.dev>
- <https://github.com/triggerdotdev/trigger.dev/releases/tag/v4.5.6>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-4672-hwv6-gq62>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-4672-hwv6-gq62/>. Everything for agents: <https://agentprime.io/llms.txt>.