Skip to content
Heist/ feed
Back to feed
MediumFix available

Trigger.dev: Cross-environment deployment cancel

Type: advisorySources: OSV

### Summary Trigger.dev isolates each project into multiple **environments** (`dev`, `staging`, `prod`, and per-PR `preview` branches), each with its **own secret API key** — the environment is a trust boundary (a `dev`/preview/CI key is lower-trust than a `prod` key). Most API routes enforce this by scoping resource lookups to the authenticated key's environment (`where: { friendlyId, runtimeEnvironmentId: auth.environment.id }`). The deployment **cancel** path does not. `DeploymentService.getDeployment()` scopes the lookup by **`projectId` only** — never `environmentId` — so a secret key for *any* environment in a project can cancel a deployment belonging to *any other* environment of the same project, including **production**. The deployment **GET** route, by contrast, *is* env-scoped — so the same key that is **404'd when trying to read** a prod deployment can nonetheless **cancel** it. That asymmetry is the bug. ### Affected `apps/webapp`, HEAD `5d99457` (current `main`). Affects self-hosted and cloud. ### Root cause `apps/webapp/app/routes/api.v1.deployments.$deploymentId.cancel.ts` authenticates to an environment and calls `deploymentService.cancelDeployment(authenticatedEnv, deploymentId, ...)`. `apps/webapp/app/v3/services/deployment.server.ts`: ```ts public cancelDeployment(authenticatedEnv: Pick, friendlyId, ...) { return this.getDeployment(authenticatedEnv.projectId, friendlyId) // projectId only .andThen(validateDeployment) // rejects only FINAL statuses .andThen

Products
trigger.dev
Affected versions
Not specified
Fixed versions
4.5.6
CVEs
CVE-2026-114079
Confirmed fixed CVEs
Not specified
Updated in this feed
31 Oct 2026, 14:08 UTC · Revision 1

Source evidence

Trigger.dev: Cross-environment deployment cancel

core-osv · Original source

Published 2 Oct 2026, 22:42 UTC

### Summary Trigger.dev isolates each project into multiple **environments** (`dev`, `staging`, `prod`, and per-PR `preview` branches), each with its **own secret API key** — the environment is a trust boundary (a `dev`/preview/CI key is lower-trust than a `prod` key). Most API routes enforce this by scoping resource lookups to the authenticated key's environment (`where: { friendlyId, runtimeEnvironmentId: auth.environment.id }`). The deployment **cancel** path does not. `DeploymentService.getDeployment()` scopes the lookup by **`projectId` only** — never `environmentId` — so a secret key for *any* environment in a project can cancel a deployment belonging to *any other* environment of the same project, including **production**. The deployment **GET** route, by contrast, *is* env-scoped — so the same key that is **404'd when trying to read** a prod deployment can nonetheless **cancel** it. That asymmetry is the bug. ### Affected `apps/webapp`, HEAD `5d99457` (current `main`). Affects self-hosted and cloud. ### Root cause `apps/webapp/app/routes/api.v1.deployments.$deploymentId.cancel.ts` authenticates to an environment and calls `deploymentService.cancelDeployment(authenticatedEnv, deploymentId, ...)`. `apps/webapp/app/v3/services/deployment.server.ts`: ```ts public cancelDeployment(authenticatedEnv: Pick, friendlyId, ...) { return this.getDeployment(authenticatedEnv.projectId, friendlyId) // projectId only .andThen(validateDeployment) // rejects only FINAL statuses .andThen

osv:GHSA-4672-hwv6-gq62

trigger.dev

Fixed versions: 4.5.6

Complete source record
{
  "id": "9ea0ccc884d86458b898f1999c0e0843e2310a3651333eae815ebc4c0199d758",
  "url": "https://osv.dev/vulnerability/GHSA-4672-hwv6-gq62",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "Trigger.dev: Cross-environment deployment cancel",
    "summary": "### Summary Trigger.dev isolates each project into multiple **environments** (`dev`, `staging`, `prod`, and per-PR `preview` branches), each with its **own secret API key** — the environment is a trust boundary (a `dev`/preview/CI key is lower-trust than a `prod` key). Most API routes enforce this by scoping resource lookups to the authenticated key's environment (`where: { friendlyId, runtimeEnvironmentId: auth.environment.id }`). The deployment **cancel** path does not. `DeploymentService.getDeployment()` scopes the lookup by **`projectId` only** — never `environmentId` — so a secret key for *any* environment in a project can cancel a deployment belonging to *any other* environment of the same project, including **production**. The deployment **GET** route, by contrast, *is* env-scoped — so the same key that is **404'd when trying to read** a prod deployment can nonetheless **cancel** it. That asymmetry is the bug. ### Affected `apps/webapp`, HEAD `5d99457` (current `main`). Affects self-hosted and cloud. ### Root cause `apps/webapp/app/routes/api.v1.deployments.$deploymentId.cancel.ts` authenticates to an environment and calls `deploymentService.cancelDeployment(authenticatedEnv, deploymentId, ...)`. `apps/webapp/app/v3/services/deployment.server.ts`: ```ts public cancelDeployment(authenticatedEnv: Pick, friendlyId, ...) { return this.getDeployment(authenticatedEnv.projectId, friendlyId) // projectId only .andThen(validateDeployment) // rejects only FINAL statuses .andThen",
    "evidence": "osv:GHSA-4672-hwv6-gq62",
    "products": [
      {
        "name": {
          "value": "trigger.dev",
          "evidence": "/affected/0/package/name"
        },
        "prerequisites": [],
        "fixed_versions": [
          {
            "value": "4.5.6",
            "evidence": "/affected/0/ranges"
          }
        ],
        "affected_versions": []
      }
    ],
    "severity": "medium",
    "structured": {
      "id": "GHSA-4672-hwv6-gq62",
      "aliases": [
        "CVE-2026-114079",
        "GHSA-4672-hwv6-gq62"
      ],
      "metrics": [
        {
          "type": "CVSS_V3",
          "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L"
        }
      ],
      "affected": [
        {
          "ranges": [
            {
              "type": "SEMVER",
              "events": [
                {
                  "introduced": "0"
                },
                {
                  "fixed": "4.5.6"
                }
              ]
            }
          ],
          "package": {
            "name": "trigger.dev",
            "purl": "pkg:npm/trigger.dev",
            "ecosystem": "npm"
          },
          "database_specific": {
            "source": "https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/10/GHSA-4672-hwv6-gq62/GHSA-4672-hwv6-gq62.json",
            "last_known_affected_version_range": "<= 4.5.5"
          }
        }
      ],
      "modified": "2026-10-21T10:57:24.966429549Z",
      "provider": "osv",
      "references": [
        "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"
      ],
      "provider_metadata": {
        "cwe_ids": [
          "CWE-639"
        ],
        "severity": "MODERATE",
        "github_reviewed": true,
        "nvd_published_at": null,
        "github_reviewed_at": "2026-10-02T22:42:40Z"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2026-114079",
        "evidence": "/aliases"
      }
    ],
    "security_relevant": true,
    "severity_evidence": "/severity/0/score"
  },
  "source_id": "core-osv",
  "document_id": 392980,
  "published_at": "2026-10-02T22:42:40+00:00"
}