Vulnerability · Published Aug 13, 2026 · Assigned by GitHub_M

CVE-2026-73654Trigger.dev: Prototype pollution via run metadata operations → process-wide cross-tenant DoS

High 8.5

In plain English

A high-severity prototype pollution in trigger.dev from triggerdotdev. Proof-of-concept exploit code is public. The chance it is exploited in the next 30 days is estimated at 0.6% (higher than 50% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)8.5High
Exploit odds (30 days)0.6%top 50.1% of all CVEs
Exploited in the wildNo reportsCISA SSVC: poc
Attack toolingNoneno public tooling known

Official description

Trigger.dev is a platform for building and deploying fully managed AI agents and workflows. From 3.3.8 until 4.5.6, the PUT /api/v1/runs/:runId/metadata endpoint passes attacker-controlled operation.key values to new JSONHeroPath(operation.key).set(newMetadata, value) in packages/core/src/v3/runMetadata/operations.ts without rejecting dangerous constructor and prototype path segments. A caller with a normal environment API key can pollute Object.prototype in the shared webapp process, corrupting Prisma queries and Prometheus labels, breaking other tenants' worker authentication, and causing a process-wide denial of service. This issue is fixed in version 4.5.6.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
npm@trigger.dev/core4.5.6GHSA-p28v-f755-9qrg

Affected products (as reported)

VendorProductVersions
triggerdotdev trigger.dev >= 3.3.8, < 4.5.6

Weakness: CWE-1321 · Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:H

References