CVE-2026-73658
Trigger.dev is a platform for building and deploying fully managed …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/triggerdotdev/trigger.dev/commit/db4074df54db06b0656becf3f974345c90fa202e
- github.com/triggerdotdev/trigger.dev/pull/3830
- github.com/triggerdotdev/trigger.dev/releases/tag/v4.5.0-rc.5
- github.com/triggerdotdev/trigger.dev/security/advisories/GHSA-888c-px7m-736v
- nvd.nist.gov/vuln/detail/CVE-2026-73658
- cve.org/CVERecord?id=CVE-2026-73658
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.