triggerdotdev trigger.dev prior 4.5.0-rc.4 Replay replayTaskRun.server.ts overrideExistingPayloadPacket runParam access control

Summaryinfo

A vulnerability was found in triggerdotdev trigger.dev. It has been classified as critical. Affected is the function overrideExistingPayloadPacket of the file apps/webapp/app/v3/services/replayTaskRun.server.ts of the component Replay. This manipulation of the argument runParam causes access control. This vulnerability is registered as CVE-2026-73657. Remote exploitation of the attack is possible. No exploit is available.

Detailsinfo

A vulnerability was found in triggerdotdev trigger.dev. It has been declared as critical. Affected by this vulnerability is the function overrideExistingPayloadPacket of the file apps/webapp/app/v3/services/replayTaskRun.server.ts of the component Replay. The manipulation of the argument runParam with an unknown input leads to a access control vulnerability. The CWE definition for the vulnerability is CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

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.

The advisory is shared at github.com. This vulnerability is known as CVE-2026-73657 since 08/13/2026. The exploitation appears to be easy. The attack can be launched remotely. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1068 for this issue.

Upgrading to version 4.5.0-rc.4 eliminates this vulnerability.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

• triggerdotdev

Name

• trigger.dev

Website

• Product: https://github.com/triggerdotdev/trigger.dev/

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion