CVE-2026-73657: triggerdotdev trigger.dev · Path Traversal
Affects triggerdotdev trigger.devSource CVE Database V5
Not known to be exploited · CVSS 4.2 Medium : upgrade to 4.5.0-rc.4 when convenient.
Data as of 11 Nov 2026, 23:24 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 4.5.0-rc.4
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 13 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 12 Nov 2026.
What to do
Upgrade triggerdotdev trigger.dev to 4.5.0-rc.4.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| triggerdotdevtrigger.dev | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
This vulnerability is fixed in trigger.dev version 4.5.0-rc.4. Users should upgrade to version 4.5.0-rc.4 or later to remediate the issue. Patch status is not explicitly confirmed beyond this fix version; check the vendor advisory for the latest remediation guidance.
Description
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.
References
- github.com/triggerdotdev/trigger.dev/security/advisories/GHSA-jx48-qfwm-xq67 (opens in a new tab)
- github.com/triggerdotdev/trigger.dev/pull/3756 (opens in a new tab)
- github.com/triggerdotdev/trigger.dev/commit/e1950778e2f2007e2d432b8f8a8fc89531c51f19 (opens in a new tab)
- github.com/triggerdotdev/trigger.dev/releases/tag/v4.5.0-rc.4 (opens in a new tab)