CVE-2026-73657— Trigger.dev: Cross-tenant payload poisoning via packet write + replay
Quick assessment
Affected
triggerdotdev trigger.dev
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.
Trigger.dev是Trigger.dev组织的一个工作流自动化开发框架。 Trigger.dev 4.4.2至4.5.0-rc.4之前版本存在安全漏洞，该漏洞源于重放任务时未进行环境ID过滤且对payload缺少完整性检查，可能导致拥有有效环境API密钥的攻击者重放其他租户的运行，消耗受害者资源并重复副作用，或通过路径遍历覆盖payload为攻击者控制的输入。
Possible ATT&CK Techniques 2 AI
T1190 · Exploit Public-Facing Application T1496 · Resource HijackingAffected Version Matrix 1
| Vendor | Product | Version Range | Status |
|---|---|---|---|
| triggerdotdev | trigger.dev | >= 4.4.2, < 4.5.0-rc.4 |
affected |
Get alerts for future matching vulnerabilities
Log in to subscribe
I. Basic Information for CVE-2026-73657
Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗
Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.
Vulnerability Title
Trigger.dev: Cross-tenant payload poisoning via packet write + replay
Source: CVE Program / CVE List V5
Vulnerability 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.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:L
Source: CVE Program / CVE List V5
Vulnerability Type
对路径名的限制不恰当(路径遍历)
Source: CVE Program / CVE List V5
Vulnerability Title
Trigger.dev 路径遍历漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Trigger.dev是Trigger.dev组织的一个工作流自动化开发框架。 Trigger.dev 4.4.2至4.5.0-rc.4之前版本存在安全漏洞，该漏洞源于重放任务时未进行环境ID过滤且对payload缺少完整性检查，可能导致拥有有效环境API密钥的攻击者重放其他租户的运行，消耗受害者资源并重复副作用，或通过路径遍历覆盖payload为攻击者控制的输入。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)
Affected Products
| Vendor | Product | Affected Versions | CPE | Subscribe |
|---|---|---|---|---|
| triggerdotdev | trigger.dev | >= 4.4.2, < 4.5.0-rc.4 | - |
|
II. Public POCs for CVE-2026-73657
| # | POC Description | Source Link | Shenlong Link |
|---|
AI-Generated POC
Premium
No public POC found.
Login to generate AI POCIII. Intelligence Information for CVE-2026-73657
请登录查看更多情报信息。
Vendor Advisories for CVE-2026-73657 (1)
Same Patch Batch · triggerdotdev · 2026-08-13 · 6 CVEs total
| CVE-2026-73656 | 9.9 CRITICAL | Trigger.dev: Cross-project deployment worker registration can modify another project's dep |
| CVE-2026-73654 | 8.5 HIGH | Trigger.dev: Prototype pollution via run metadata operations → process-wide cross-tenant D |
| CVE-2026-73658 | 8.2 HIGH | Trigger.dev: Cross-tenant object store read and write via URL path traversal |
| CVE-2026-73659 | 8.1 HIGH | Trigger.dev: Cross-tenant object read/write via path traversal in packet presign API |
| CVE-2026-73655 | 7.4 HIGH | Trigger.dev: Account Takeover via Cross-Provider OAuth Email Matching in Google Login |
IV. Related Vulnerabilities
Same product: trigger.dev
-
CVE-2026-92773
Trigger.dev before 4.6.0 GitHub App Installation Takeover -
CVE-2026-85651
Trigger.dev before 4.5.2 Unauthorized Environment Access via -
CVE-2026-85650
Trigger.dev before 4.5.2 Server-Side Request Forgery via web -
CVE-2026-73659
Trigger.dev: Cross-tenant object read/write via path travers -
CVE-2026-73658
Trigger.dev: Cross-tenant object store read and write via UR
Same vendor: triggerdotdev
-
CVE-2026-92773
Trigger.dev before 4.6.0 GitHub App Installation Takeover -
CVE-2026-85651
Trigger.dev before 4.5.2 Unauthorized Environment Access via -
CVE-2026-85650
Trigger.dev before 4.5.2 Server-Side Request Forgery via web -
CVE-2026-73659
Trigger.dev: Cross-tenant object read/write via path travers -
CVE-2026-73658
Trigger.dev: Cross-tenant object store read and write via UR
Same weakness: CWE-22
-
CVE-2026-63266
Arbitrary file write via calcext:data-mappings, sql provider -
CVE-2026-105286
Totolink A3002MU File Upload formUploadFile sub_44B250 path -
CVE-2026-104805
Mitel MiVoice Office 400 Backup Restoration Arbitrary File W -
CVE-2026-105293
Legcord 1.1.0 through 1.3.0 Path Traversal via Theme IPC Han -
CVE-2026-105174
Gerapy Project Management views.py project_create path trave
V. Comments for CVE-2026-73657
No comments yet