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

published 2026-08-13 2 mo ago modified 2026-09-18 51 d ago also GHSA-p28v-f755-9qrg , EUVD-2026-58358

cvss: 8.5; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.6%; EPSS 0.6% chance of exploitation in 30 days, percentile 49%
public exploits: 0; none known

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.

Patch / fix

fixed in 1 links 3

npm @trigger.dev/core 4.5.6

github.com/triggerdotdev/trigger.dev@6997aeb commit
github.com/triggerdotdev/trigger.dev#4316 pull request
github.com/triggerdotdev/trigger.dev/releases/tag/v4.5.6 release

CISA SSVC

Exploitation: Proof of concept is public
Automatable: no
Technical impact: partial
Assessed: 2 mo ago (2026-08-14)

Exploit prediction

0.62% chance of exploitation in the next 30 days, higher than 49% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

github.com https://github.com/triggerdotdev/trigger.dev/security/advisories/GHSA-p28v-f755-9qrg referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
CNA	3.1	8.5	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:H
GitHub	3.1	8.5	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:H

Affected packages

ecosystem	package	affected	fixed in
npm	@trigger.dev/core	>=3.3.8, <4.5.6	4.5.6

Affected products

triggerdotdev trigger.dev

Classification

Weakness

CWE-1321 Improperly Controlled Modification of Object Prototype Attributes

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary