CyberRota Analysis
AI-GeneratedThe vulnerability affects the Trigger.dev platform, specifically in versions 4.4.2 to 4.5.0-rc.5, where improper handling of user-controlled packet keys allows unauthorized access to presigned URLs for object-store keys. This could enable an attacker with a valid environment API key to read or overwrite task payloads belonging to other tenants, posing a significant risk of data exposure and integrity compromise. Organizations using affected versions should prioritize upgrading to version 4.5.0-rc.5 to mitigate this high-severity vulnerability.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD 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.