Trigger.dev是Trigger.dev组织的一个工作流自动化开发框架。 Trigger.dev 4.4.2版本至4.5.0-rc.5之前版本存在安全漏洞,该漏洞源于Aws4FetchClient.buildUrl()和Aws4FetchClient.presign()函数将用户控制的数据包密钥分配给URL.pathname,且API端点未拒绝点段及验证资源所有权,可能导致具有有效环境API密钥的调用者获取其他租户的预签名URL,读取或覆盖任务负载。
| Vendor | Product | Version Range | Status |
|---|---|---|---|
| triggerdotdev | trigger.dev | >= 4.4.2, < 4.5.0-rc.5 |
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 | >= 4.4.2, < 4.5.0-rc.5 | - |
|
| # | 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-73654 | 8.5 HIGH | Trigger.dev: Prototype pollution via run metadata operations → process-wide cross-tenant D |
| 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