Trigger.dev是Trigger.dev组织的一个工作流自动化开发框架。 Trigger.dev 3.3.8版本至4.5.6之前版本存在输入验证错误漏洞,该漏洞源于PUT /api/v1/runs/:runId/metadata端点将攻击者控制的operation.key值传递给JSONHeroPath操作,而未拒绝危险的构造函数和原型路径段,可能导致攻击者污染Object.prototype,破坏Prisma查询和Prometheus标签,破坏其他租户的worker身份验证,并导致进程范围的拒绝服
| Vendor | Product | Version Range | Status |
|---|---|---|---|
| triggerdotdev | trigger.dev | >= 3.3.8, < 4.5.6 |
affected |
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.
| Vendor | Product | Affected Versions | CPE | Subscribe |
|---|---|---|---|---|
| triggerdotdev | trigger.dev | >= 3.3.8, < 4.5.6 | - |
|
| # | POC Description | Source Link | Shenlong Link |
|---|
No public POC found.
Login to generate AI POC| CVE-2026-73656 | 9.9 CRITICAL | Trigger.dev: Cross-project deployment worker registration can modify another project's dep |
| 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 |
| CVE-2026-73657 | 4.2 MEDIUM | Trigger.dev: Cross-tenant payload poisoning via packet write + replay |
No comments yet