Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Fri, 14 Aug 2026 10:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Triggerdotdev
Triggerdotdev trigger.dev |
|
| Vendors & Products |
Triggerdotdev
Triggerdotdev trigger.dev |
Thu, 13 Aug 2026 21:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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.5, Aws4FetchClient.buildUrl() and Aws4FetchClient.presign() in apps/webapp/app/v3/objectStoreClient.server.ts assign user-controlled packet keys to URL.pathname, while apps/webapp/app/routes/api.v1.packets.$.ts accepts params["*"] without rejecting dot segments and uses findResource: async () => 1 without per-resource ownership validation. WHATWG path normalization collapses .. segments before signing, allowing a caller with a valid environment API key to obtain presigned URLs for another tenant's object-store keys and read or overwrite task payloads. This issue is fixed in version 4.5.0-rc.5. | |
| Title | Trigger.dev: Cross-tenant object store read and write via URL path traversal | |
| Weaknesses | CWE-20 CWE-22 CWE-862 |
|
| References |
|
|
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-08-14T16:30:13.661Z
Reserved: 2026-08-13T14:04:09.605Z
Link: CVE-2026-73658
No data.
Status : Received
Published: 2026-08-13T22:17:27.190
Modified: 2026-08-14T17:20:35.837
Link: CVE-2026-73658
No data.
OpenCVE Enrichment
Updated: 2026-08-14T09:30:28Z