Vulnerabilities in pkg:npm/@trigger.dev/core

PACKAGE
Advisory Identifier: GHSA-p28v-f755-9qrg
Advisory Summary

CVE-2026-73654 is a HIGH (CVSS 8.5) denial of service vulnerability (CWE-1321: Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')) affecting @trigger.dev/core libraries in the npm ecosystem. The issue involves prototype pollution via run metadata operations → process-wide cross-tenant dos. Remediation is available by upgrading affected packages to version 4.5.6.

1 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:npm/@trigger.dev/core

1 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:npm/@trigger.dev/core. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-p28v-f755-9qrg CVE-2026-73654 HIGH Trigger.dev: Prototype pollution via run metadata operations → process-wide cross-tenant DoS

CVE-2026-73654 at a Glance

CVE Identifier CVE-2026-73654
GHSA Identifier GHSA-p28v-f755-9qrg
Severity HIGH
CVSS v3.1 Base Score 8.5
CWE Classification CWE-1321: Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')
Affected Product @trigger.dev/core
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 8.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Changed (S:C)
Confidentiality None (C:N)
Integrity Low (I:L)
Availability High (A:H)

How to Fix CVE-2026-73654

To remediate this vulnerability, upgrade all affected @trigger.dev/core dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

@trigger.dev/core fixed: 4.5.6
npm install @trigger.dev/core@4.5.6
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls @trigger.dev/core

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-73654, inspect your project dependencies using npm:

npm ls @trigger.dev/core

Analyze the terminal output to locate any version of @trigger.dev/core in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 4.5.6), your application is affected.

Note: The npm ls @trigger.dev/core command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-1321: Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution'), where the product receives input from an upstream component that specifies attributes that are to be initialized or updated in an object, but it does not properly control modifications of attributes of the object prototype. In @trigger.dev/core, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## Summary The run-metadata update endpoint `PUT /api/v1/runs/:runId/metadata` applies client-supplied "operations" by passing the **attacker-controlled `operation.key`** straight into `new JSONHeroPath(operation.key).set(newMetadata, value)` (`packages/core/src/v3/runMetadata/operations.ts:22-23`), with **no prototype-pollution guard** (`@jsonhero/path@^1.0.21` does not reject `__proto__`/`constructor`/`prototype`). A request with `key: "$.__proto__.polluted"` sets **`Object.prototype.polluted`** in the webapp process. Because every plain object then inherits that property, it corrupts unrelated code **process-wide and across tenants** — including Prisma query building and the Prometheus metrics client — causing query failures, **broken authentication for other tenants' workers**, and an `uncaughtException` (denial of service). Only a normal, low-privilege environment API key is required (one request). ## Severity A single request from any holder of a normal environment API key contaminates `Object.prototype` in the shared webapp process, breaking other tenants' workers (scope change) and degrading/ crashing the process (high availability impact). Prototype pollution is also a primitive for further gadget chains (integrity/confidentiality). ## Affected versions - **Introduced** in commit `34f8bd588` ("Add ability to update parent and root run metadata from children", PR #1563, 2025-01-08) — the `JSONHeroPath(operation.key).set()` sink is present from the first commit of `operations.ts`. SDK was at `3.3.8` at that time. - **Still present at HEAD** (SDK `4.5.0-rc.7`); `operations.ts` unchanged since 2025-05, and `@jsonhero/path` is pinned at `^1.0.21` (no proto-guard) throughout. - **Affected range:** `>= v3.3.8` (metadata operations API) through `v4-beta` / current v4.x — **fixed: 4.5.6**. ## Root cause `packages/core/src/v3/runMetadata/operations.ts` — `applyMetadataOperations()` builds a path from the **untrusted** `operation.key` and writes to it, for every operation type (`set`, `append`, `increment`, …): ```ts const path = new JSONHeroPath(operation.key); // operation.key fully attacker-controlled path.set(newMetadata, operation.value); // no __proto__/constructor/prototype rejection ``` The request schema (`UpdateMetadataRequestBody`) types `key` as a plain string with no validation, and `@jsonhero/path@1.0.21` walks `__proto__` as an ordinary segment → the assignment lands on `Object.prototype`. ## Proof of Concept Self-host `ghcr.io/triggerdotdev/trigger.dev:v4-beta`. Authenticated with a **normal environment API key** (`tr_dev_…`) and any run id of that environment. ```bash curl -X PUT "http://localhost:8030/api/v1/runs/run_cmqr2bsyo00013js2twwhdsfu/metadata" \ -H "Authorization: Bearer tr_dev_<env_key>" -H "Content-Type: application/json" \ --data '{"operations":[{"type":"set","key":"$.__proto__.polluted","value":"PWNED"}]}' ``` **Result — `Object.prototype.polluted = "PWNED"` process-wide.** Observed in the webapp logs: 1. **The request's own query is corrupted** — `polluted:"PWNED"` injected into every object Prisma enumerates: ``` prisma.taskRun.updateMany({ where:{ id:"…", metadataVersion:2, polluted:"PWNED" }, data:{ …, metadataVersion:{ increment:1, polluted:"PWNED" }, polluted:"PWNED" }, polluted:"PWNED" }) -> Unknown argument `polluted` ``` 2. **Cross-tenant authentication break** — the *next* request from a different client (a worker's `POST /engine/v1/dev/dequeue`) fails inside `findEnvironmentByApiKey`: ``` prisma.runtimeEnvironment.findFirst({ where:{ apiKey:"…", polluted:"PWNED" }, include:{ project:true, …, polluted:"PWNED" } }) -> PrismaClientValidationError ``` i.e. one tenant's request **breaks authentication for other tenants' workers** → their jobs stop being dequeued/processed. 3. **Denial of service — full process crash.** The `uncaughtException` in prom-client (`Error: Added label "polluted" is not included in initial labelset: [ 'kind' ]`) **crashes the webapp process**. Demonstrated with a second tenant: Tenant B (a *different* org/env, with its own API key) had a working request (`POST /engine/v1/dev/dequeue` → HTTP 400, auth OK) **before** the attack; **immediately after Tenant A's single attack request, B's request returned HTTP 000 (no response) — the whole multi-tenant webapp was down**. Logs show the crash at 20:53:41 and the process auto-restarting ~3s later (`FairQueue/ScheduleEngine started`). Repeating the attack in a loop yields a **crash-loop = sustained DoS for all tenants**. *(Note: the metadata endpoint itself swallows the Prisma failure with `ignoreError:true` and still returns HTTP 200 — the damage is the process-wide contamination observed in the logs, not the endpoint's status code.)* ## Impact A low-privilege caller (one normal environment API key, one request) pollutes `Object.prototype` in the shared multi-tenant webapp process, causing: - **Full cross-tenant denial of service** — the resulting `uncaughtException` **crashes the webapp process**, taking the service down for **all tenants** (demonstrated: a second tenant's request returned HTTP 000 immediately after the attack). Repeating the request produces a **crash-loop / sustained DoS**. Even without the crash, contaminated Prisma queries break other tenants' worker authentication, halting job processing. - **A prototype-pollution primitive** usable for further gadget chains (auth/logic bypass, etc.). ## Suggested remediation 1. **Reject dangerous path segments** in `operation.key` before building the path — block `__proto__`, `constructor`, `prototype` (and validate the `$.`-rooted JSONHero path shape). 2. **Build metadata on a null-prototype object** (`Object.create(null)`) and/or use a pollution-safe setter, so `__proto__` cannot reach `Object.prototype`. 3. Upgrade/replace `@jsonhero/path` for a version that is prototype-pollution safe, or wrap its `.set()` with a guard.

CVE-2026-73654 Affected @trigger.dev/core Versions

1 component(s)
Fixed Versions:
4.5.6
Product / Package Ecosystem Affected Versions Fixed Version
@trigger.dev/core
npm
≥ 3.3.8
< 4.5.6
4.5.6

References

Frequently Asked Questions

What is CVE-2026-73654?
CVE-2026-73654 is a security vulnerability in @trigger.dev/core involving Prototype pollution via run metadata operations → process-wide cross-tenant DoS under CWE-1321: Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution').
Which @trigger.dev/core versions are affected?
Affected versions include releases prior to 4.5.6 across affected packages: @trigger.dev/core.
What version fixes CVE-2026-73654?
Upgrading to 4.5.6 (or the latest patched release for your respective branch) resolves the vulnerability.
Is @trigger.dev/core affected?
Yes, @trigger.dev/core is affected in releases prior to 4.5.6. Upgrade your dependency to 4.5.6 or later.
What is the CVSS score of CVE-2026-73654?
CVE-2026-73654 has a CVSS v3.1 base score of 8.5 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:H.
What CWE is associated with CVE-2026-73654?
CVE-2026-73654 is classified under CWE-1321: Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') (The product receives input from an upstream component that specifies attributes that are to be initialized or updated in an object, but it does not properly control modifications of attributes of the object prototype.).
How can I check npm dependencies for CVE-2026-73654?
Run the dependency tree command: 'npm ls @trigger.dev/core'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-p28v-f755-9qrg",
  "modified" : "2026-08-13T20:54:11Z",
  "published" : "2026-08-13T20:54:11Z",
  "aliases" : [ "CVE-2026-73654" ],
  "summary" : "Trigger.dev: Prototype pollution via run metadata operations → process-wide cross-tenant DoS",
  "details" : "## Summary\n\nThe run-metadata update endpoint `PUT /api/v1/runs/:runId/metadata` applies client-supplied\n\"operations\" by passing the **attacker-controlled `operation.key`** straight into\n`new JSONHeroPath(operation.key).set(newMetadata, value)`\n(`packages/core/src/v3/runMetadata/operations.ts:22-23`), with **no prototype-pollution guard**\n(`@jsonhero/path@^1.0.21` does not reject `__proto__`/`constructor`/`prototype`).\n\nA request with `key: \"$.__proto__.polluted\"` sets **`Object.prototype.polluted`** in the webapp\nprocess. Because every plain object then inherits that property, it corrupts unrelated code\n**process-wide and across tenants** — including Prisma query building and the Prometheus metrics\nclient — causing query failures, **broken authentication for other tenants' workers**, and an\n`uncaughtException` (denial of service). Only a normal, low-privilege environment API key is\nrequired (one request).\n\n## Severity\n\nA single request from any holder of a normal environment API key contaminates `Object.prototype`\nin the shared webapp process, breaking other tenants' workers (scope change) and degrading/\ncrashing the process (high availability impact). Prototype pollution is also a primitive for\nfurther gadget chains (integrity/confidentiality).\n\n## Affected versions\n\n- **Introduced** in commit `34f8bd588` (\"Add ability to update parent and root run metadata from\n  children\", PR #1563, 2025-01-08) — the `JSONHeroPath(operation.key).set()` sink is present from\n  the first commit of `operations.ts`. SDK was at `3.3.8` at that time.\n- **Still present at HEAD** (SDK `4.5.0-rc.7`); `operations.ts` unchanged since 2025-05, and\n  `@jsonhero/path` is pinned at `^1.0.21` (no proto-guard) throughout.\n- **Affected range:** `>= v3.3.8` (metadata operations API) through `v4-beta` / current v4.x —\n  **fixed: 4.5.6**.\n\n## Root cause\n\n`packages/core/src/v3/runMetadata/operations.ts` — `applyMetadataOperations()` builds a path from\nthe **untrusted** `operation.key` and writes to it, for every operation type (`set`, `append`,\n`increment`, …):\n\n```ts\nconst path = new JSONHeroPath(operation.key);   // operation.key fully attacker-controlled\npath.set(newMetadata, operation.value);         // no __proto__/constructor/prototype rejection\n```\n\nThe request schema (`UpdateMetadataRequestBody`) types `key` as a plain string with no validation,\nand `@jsonhero/path@1.0.21` walks `__proto__` as an ordinary segment → the assignment lands on\n`Object.prototype`.\n\n## Proof of Concept\n\nSelf-host `ghcr.io/triggerdotdev/trigger.dev:v4-beta`. Authenticated with a **normal environment\nAPI key** (`tr_dev_…`) and any run id of that environment.\n\n```bash\ncurl -X PUT \"http://localhost:8030/api/v1/runs/run_cmqr2bsyo00013js2twwhdsfu/metadata\" \\\n  -H \"Authorization: Bearer tr_dev_<env_key>\" -H \"Content-Type: application/json\" \\\n  --data '{\"operations\":[{\"type\":\"set\",\"key\":\"$.__proto__.polluted\",\"value\":\"PWNED\"}]}'\n```\n\n**Result — `Object.prototype.polluted = \"PWNED\"` process-wide.** Observed in the webapp logs:\n\n1. **The request's own query is corrupted** — `polluted:\"PWNED\"` injected into every object Prisma\n   enumerates:\n   ```\n   prisma.taskRun.updateMany({ where:{ id:\"…\", metadataVersion:2, polluted:\"PWNED\" },\n     data:{ …, metadataVersion:{ increment:1, polluted:\"PWNED\" }, polluted:\"PWNED\" }, polluted:\"PWNED\" })\n   -> Unknown argument `polluted`\n   ```\n2. **Cross-tenant authentication break** — the *next* request from a different client (a worker's\n   `POST /engine/v1/dev/dequeue`) fails inside `findEnvironmentByApiKey`:\n   ```\n   prisma.runtimeEnvironment.findFirst({ where:{ apiKey:\"…\", polluted:\"PWNED\" },\n     include:{ project:true, …, polluted:\"PWNED\" } })  -> PrismaClientValidationError\n   ```\n   i.e. one tenant's request **breaks authentication for other tenants' workers** → their jobs stop\n   being dequeued/processed.\n3. **Denial of service — full process crash.** The `uncaughtException` in prom-client\n   (`Error: Added label \"polluted\" is not included in initial labelset: [ 'kind' ]`) **crashes the\n   webapp process**. Demonstrated with a second tenant: Tenant B (a *different* org/env, with its\n   own API key) had a working request (`POST /engine/v1/dev/dequeue` → HTTP 400, auth OK) **before**\n   the attack; **immediately after Tenant A's single attack request, B's request returned HTTP 000\n   (no response) — the whole multi-tenant webapp was down**. Logs show the crash at 20:53:41 and the\n   process auto-restarting ~3s later (`FairQueue/ScheduleEngine started`). Repeating the attack in a\n   loop yields a **crash-loop = sustained DoS for all tenants**.\n\n*(Note: the metadata endpoint itself swallows the Prisma failure with `ignoreError:true` and still\nreturns HTTP 200 — the damage is the process-wide contamination observed in the logs, not the\nendpoint's status code.)*\n\n## Impact\n\nA low-privilege caller (one normal environment API key, one request) pollutes `Object.prototype`\nin the shared multi-tenant webapp process, causing:\n\n- **Full cross-tenant denial of service** — the resulting `uncaughtException` **crashes the webapp\n  process**, taking the service down for **all tenants** (demonstrated: a second tenant's request\n  returned HTTP 000 immediately after the attack). Repeating the request produces a **crash-loop /\n  sustained DoS**. Even without the crash, contaminated Prisma queries break other tenants' worker\n  authentication, halting job processing.\n- **A prototype-pollution primitive** usable for further gadget chains (auth/logic bypass, etc.).\n\n## Suggested remediation\n\n1. **Reject dangerous path segments** in `operation.key` before building the path — block\n   `__proto__`, `constructor`, `prototype` (and validate the `$.`-rooted JSONHero path shape).\n2. **Build metadata on a null-prototype object** (`Object.create(null)`) and/or use a\n   pollution-safe setter, so `__proto__` cannot reach `Object.prototype`.\n3. Upgrade/replace `@jsonhero/path` for a version that is prototype-pollution safe, or wrap its\n   `.set()` with a guard.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@trigger.dev/core"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "3.3.8"
      }, {
        "fixed" : "4.5.6"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 4.5.5"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/triggerdotdev/trigger.dev/security/advisories/GHSA-p28v-f755-9qrg"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/triggerdotdev/trigger.dev/pull/4316"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/triggerdotdev/trigger.dev/commit/6997aeb05e27d2db47f9eda01fdc8a17c81a1ae0"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/triggerdotdev/trigger.dev"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/triggerdotdev/trigger.dev/releases/tag/v4.5.6"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-1321" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-08-13T20:54:11Z",
    "nvd_published_at" : null
  }
}