CVE-2026-73654: Trigger.dev: Prototype pollution via run metadata operations → process-wide cross-tenant DoS
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 Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
trigger.devto a version that resolves this vulnerability.Fixed in 4.5.6
Event History
Frequently Asked Questions
What is the severity of CVE-2026-73654?
The severity of CVE-2026-73654 is rated high with a score of 8.5.
How do I fix CVE-2026-73654?
To mitigate CVE-2026-73654, upgrade to Trigger.dev version 4.5.7 or later that has the vulnerability patched.
What types of attacks are possible with CVE-2026-73654?
CVE-2026-73654 allows for prototype pollution that can lead to process-wide cross-tenant Denial of Service (DoS) attacks.
Which software is affected by CVE-2026-73654?
CVE-2026-73654 affects Trigger.dev versions from 3.3.8 to 4.5.6.
What components are involved in CVE-2026-73654?
The vulnerability in CVE-2026-73654 involves the PUT /api/v1/runs/:runId/metadata endpoint processing attacker-controlled operation.key values.