CVE-2026-73657 PUBLISHED

Trigger.dev: Cross-tenant payload poisoning via packet write + replay

Assigner: GitHub_M
Reserved: 13.08.2026 Published: 13.08.2026 Updated: 13.08.2026

Trigger.dev is a platform for building and deploying fully managed AI agents and workflows. From 4.4.2 until 4.5.0-rc.4, POST /api/v1/runs/:runParam/replay in apps/webapp/app/routes/api.v1.runs.$runParam.replay.ts uses prisma.taskRun.findUnique({ where: { friendlyId: runParam } }) without a runtimeEnvironmentId filter, then ReplayTaskRunService in apps/webapp/app/v3/services/replayTaskRun.server.ts replays the selected run in the victim environment. Any valid environment API key can therefore replay another tenant's run by friendlyId, consuming victim resources and repeating side effects; when payloadType: "application/store" is used, overrideExistingPayloadPacket() calls conditionallyImportPacket() on existingTaskRun.payload without an integrity check, so payload bytes overwritten through a separate object-store path-traversal vulnerability become attacker-controlled input to the victim task. This issue is fixed in version 4.5.0-rc.4.

Metrics

CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:L
CVSS Score: 4.2

Product Status

Vendor triggerdotdev
Product trigger.dev
Versions
  • Version >= 4.4.2, < 4.5.0-rc.4 is affected

References

Problem Types

  • CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') CWE
  • CWE-345: Insufficient Verification of Data Authenticity CWE
  • CWE-639: Authorization Bypass Through User-Controlled Key CWE