Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') Affecting trigger-dev package, versions <4.5.6-r0


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.62% (48th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-MINIMOSLATEST-TRIGGERDEV-18857252
  • published16 Aug 2026
  • disclosed13 Aug 2026

Introduced: 13 Aug 2026

CVE-2026-73654  (opens in a new tab)
CWE-1321  (opens in a new tab)

How to fix?

Upgrade Minimos:latest trigger-dev to version 4.5.6-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream trigger-dev package and not the trigger-dev package as distributed by Minimos. See How to fix? for Minimos:latest relevant fixed versions and status.

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.