CVE-2026-114083: Trigger.dev before 4.5.0-rc.3 Path Traversal via Packets Presigned URL Endpoints
triggerdotdev · trigger.dev
Fixed in 4.5.0-rc.3 · Affected: triggerdotdev trigger.dev before 4.5.0-rc.3 · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 43% of scored CVEs
DescriptionCVE.org
Trigger.dev before 4.5.0-rc.3 contains a path traversal vulnerability in the api/v1/packets and api/v2/packets endpoints that allows authenticated tenants to escape their object key prefix through an unsanitized filename splat segment. Attackers holding one valid API key can supply ../ sequences to obtain presigned GET or PUT URLs and read or overwrite other tenants' run payloads and outputs.
Affected products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- triggerdotdev · trigger.devbefore 4.5.0-rc.3
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- triggerdotdev
- Published
- October 2026
CoverageNo articles yet
No CyberSIXT article names CVE-2026-114083 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.