CVE-2026-73654
CVE-2026-73654 · Trigger.dev: Prototype pollution via run metadata operations → process-wide cross-tenant DoS
This page contains facts from public vulnerability sources. Check the original advisory before updating.
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.
CVSS 8.5 · High · EPSS 0.6% · Fix available
- Published
- Updated
Stack: node
Affected products and versions
trigger.dev
- Versions
- >= 3.3.8, < 4.5.6: Affected
No fix published
@trigger.dev/core npm
- Affected ranges
- SEMVER: ≥ 3.3.8, < 4.5.6
Update to 4.5.6
Original sources
- https://github.com/triggerdotdev/trigger.dev/security/advisories/GHSA-p28v-f755-9qrg
- https://github.com/triggerdotdev/trigger.dev/pull/4316
- https://github.com/triggerdotdev/trigger.dev/commit/6997aeb05e27d2db47f9eda01fdc8a17c81a1ae0
- https://github.com/triggerdotdev/trigger.dev/releases/tag/v4.5.6
- https://nvd.nist.gov/vuln/detail/CVE-2026-73654