EUVD-2026-58479Severity by source
AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:L
Cross-tenant replay crosses tenant security boundaries warranting S:C; AC:H reflects needing victim friendlyId; PR:L for any valid API key; no direct confidentiality disclosure confirmed.
Primary rating from Vendor (GitHub_M).
CVSS VectorVendor: GitHub_M
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:L
Lifecycle Timeline
3DescriptionCVE.org
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.
AnalysisAI
Cross-tenant run replay in Trigger.dev 4.4.2-4.5.0-rc.3 allows any authenticated API key holder to replay task runs belonging to other tenants by supplying a victim's run friendlyId to the replay endpoint, which performs no tenant isolation check. This unauthorized replay consumes victim compute resources and re-executes side effects such as outbound API calls, webhook triggers, and database writes. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | The cross-tenant replay flaw requires: (1) the attacker holds any valid Trigger.dev environment API key (PR:L - a legitimate developer account suffices; no admin privilege is needed); and (2) the attacker can identify or enumerate the `friendlyId` of a run belonging to a different tenant - IDs are not inherently secret and may appear in logs, error messages, or be derivable from patterns. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The NVD CVSS 3.1 score of 4.2 (AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:L) captures the authenticated and high-complexity nature of the attack but likely understates real-world business impact in multi-tenant SaaS deployments. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker holding a legitimately obtained or compromised Trigger.dev environment API key enumerates or guesses a `friendlyId` from a victim tenant's task run (IDs may follow predictable patterns or be discoverable via shared logs or error messages), then issues `POST /api/v1/runs/{victim-friendlyId}/replay` using their own key. Because the replay endpoint queries by `friendlyId` without a tenant filter, the request succeeds and `ReplayTaskRunService` executes the run in the victim's environment - consuming their compute quota and re-firing any side effects such as payment webhooks or third-party API mutations. … |
| Remediation | Upgrade to Trigger.dev version 4.5.0-rc.4, which introduces the `runtimeEnvironmentId` tenant scope filter in the replay endpoint's database query and adds integrity verification in `overrideExistingPayloadPacket()`. … Detailed patch versions, workarounds, and compensating controls in full report. |
Threat intelligence, references, and detailed analysis are available after sign-in.
More in Trigger Dev
View allPrototype pollution in Trigger.dev's run metadata API (versions 3.3.8 through 4.5.5) lets any authenticated tenant corru
Cross-tenant authorization bypass in Trigger.dev before 4.5.6 lets a caller holding a valid API key for one project act
Cross-tenant path traversal in Trigger.dev versions 4.4.2 through pre-4.5.0-rc.5 allows any authenticated tenant holding
Path traversal in Trigger.dev's packet presign API routes (versions 4.4.2 through 4.4.x) allows a holder of any valid pr
Account takeover in Trigger.dev before 4.5.2 allows an unauthenticated remote attacker to hijack any existing user accou
Same weakness CWE-22 – Path Traversal
View allSame technique Path Traversal
View allShare
External POC / Exploit Code
Leaving vuln.today