CVE-2026-73654 Trigger.dev: Prototype pollution via run metadata operations → process-wide cross-tenant DoS
Attackers can pollute Object.prototype via metadata operations, causing process-wide denial of service affecting all tenants.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-73654?
CVE-2026-73654 is a high-severity code injection vulnerability in triggerdotdev trigger.dev, published on 13 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
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.
Weakness: CWE-1321
Which versions are affected by CVE-2026-73654?
2 open source packages ship an affected version, including @trigger.dev/core.
| Package | Affected | Fixed in |
|---|---|---|
@trigger.dev/core npm | From 3.3.8 | 4.5.6 |
@trigger.dev/core npm | From 3.3.8 | 4.5.6 |
How do I fix CVE-2026-73654?
Upgrade @trigger.dev/core to 4.5.6 or later.
Upgrade, and never evaluate templates, expressions or code built from user input. More about Code injection.
Is CVE-2026-73654 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-73654 exists.
Sources
Also known as GHSA-p28v-f755-9qrg, MINI-763p-gp56-9ph8.