Is CVE-2026-114083 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-114083 being exploited in the wild.

How severe is CVE-2026-114083?

High severity, with a CVSS score of 8.1, published 21 October 2026.

Is there a fix for CVE-2026-114083?

Yes: fixed in 4.5.0-rc.3. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-114083 attacked?

It is attacked over the network.

Am I affected by CVE-2026-114083?

Check whether you run Trigger.dev at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-114083: Trigger.dev path traversal in packet endpoints

CVE-2026-114083 · Severity: high · CVSS 8.1 · Published 2026-10-21

Trigger.dev is a task execution and workflow platform that stores large payloads in cloud object storage and uses presigned URLs to let SDKs and workers access them. An authenticated attacker with any valid API key can exploit unsanitized filename parameters in the packet endpoints to traverse directories, obtaining presigned URLs that grant read and write access to other tenants' stored payloads and outputs—which commonly contain secrets, credentials, and personally identifiable information.

Technologies: Trigger.dev. Vendors: Trigger.dev.

Quick answers

Is CVE-2026-114083 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-114083 being exploited in the wild.
How severe is CVE-2026-114083?: High severity, with a CVSS score of 8.1, published 21 October 2026.
Which products and versions are affected?: Trigger.dev before 4.5.0-rc.3.
Is there a fix for CVE-2026-114083?: Yes: fixed in 4.5.0-rc.3. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-114083 attacked?: It is attacked over the network.
Am I affected by CVE-2026-114083?: Check whether you run Trigger.dev at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: 4.5.0-rc.3

Technical details

The vulnerability is a path traversal flaw in the api/v1/packets and api/v2/packets endpoints (apps/webapp/app/routes/api.v1.packets.$.ts and api.v2.packets.$.ts) where the filename splat parameter is passed directly to generatePresignedUrl() without sanitization of ../ sequences. The presigned URL is constructed by concatenating packets/${projectRef}/${envSlug}/${filename} and then URL-encoding it; the WHATWG URL parser normalizes ../ segments before the aws4fetch client signs the request, allowing an attacker to resolve the key outside their own environment's prefix into any other tenant's directory. The vulnerable configuration is the default self-hosted deployment using static object store credentials (MinIO), which normalizes traversal patterns; AWS SDK backend deployments percent-encode dots and are less affected. Requires one valid secret API key for any environment the attacker controls.

Affected products

Trigger.dev Trigger.dev before 4.5.0-rc.3

Timeline

2026-07-09: disclosed
2026-10-21: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.