CVE-2026-73657

Received Received - Intake

Privilege Escalation in Trigger.dev via ReplayTaskRunService

Publication date: 2026-08-13

Last updated on: 2026-08-13

Assigner: GitHub, Inc.

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-08-13

Last Modified

2026-08-13

Generated

2026-08-14

AI Q&A

2026-08-14

EPSS Evaluated

N/A

NVD

CVE-2026-73657

Affected Vendors & Products

Vendor	Product	Version / Range
trigger.dev	trigger.dev	From 4.4.2 (inc) to 4.5.0-rc.4 (inc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-22	The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
CWE-345	The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data.
CWE-639	The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.

Attack-Flow Graph

Executive Summary

This vulnerability in Trigger.dev allows an attacker with a valid environment API key to replay another tenant's task run by its friendly ID. The issue occurs because the replay endpoint does not filter by runtimeEnvironmentId, enabling cross-tenant replay attacks. Additionally, when specific payload types are used, attacker-controlled input can overwrite existing task run payloads through a path-traversal vulnerability, leading to potential data corruption or unauthorized execution.

Detection Guidance

This vulnerability involves unauthorized replay of task runs in Trigger.dev due to missing runtimeEnvironmentId filtering. To detect it, inspect API logs for POST requests to /api/v1/runs/:runParam/replay with valid environment API keys accessing runs outside their tenant scope. Check for payloadType application/store with overridden payload bytes via path traversal.

Impact Analysis

This vulnerability could allow unauthorized users to consume your resources, repeat side effects, or manipulate task executions in your environment. Attackers might replay your task runs, overwrite payload data, or trigger unintended actions, potentially disrupting workflows or causing data integrity issues.

Compliance Impact

This vulnerability could lead to unauthorized access or replay of another tenant's data, potentially violating GDPR's data protection principles (e.g., integrity, confidentiality) and HIPAA's requirements for safeguarding protected health information. Unauthorized replay of tasks may also result in non-compliance with data processing agreements or regulatory audits due to lack of audit trail integrity.

Mitigation Strategies

Upgrade Trigger.dev to version 4.5.0-rc.4 or later to address the vulnerability. Review environment API keys for unauthorized access and revoke any suspicious keys. Monitor task runs for unexpected replay activity or resource consumption.

Hi! I’m here to help you understand CVE-2026-73657. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70