Is CVE-2026-73658 exploited in the wild?

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

How severe is CVE-2026-73658?

High severity, with a CVSS score of 8.2, published 13 August 2026.

Which products and versions are affected?

Trigger.dev 4.4.2 to 4.5.0-rc.4.

Is there a fix for CVE-2026-73658?

A patch was published on 2026-06-05: Fix merged in PR #3830, released in version 4.5.0-rc.5 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-73658 attacked?

It is attacked over the network, in a hosted service.

Am I affected by CVE-2026-73658?

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-73658: Trigger.dev path traversal in presigned URLs

CVE-2026-73658 · Severity: high · CVSS 8.2 · Published 2026-08-13

Trigger.dev is a platform for building and deploying AI agents and workflows. A path traversal vulnerability in versions 4.4.2 through 4.5.0-rc.4 allowed authenticated users with valid API keys to bypass storage isolation and access or modify other tenants' task payloads by crafting specially-formatted presigned URLs that escape the intended storage prefix.

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

Quick answers

Is CVE-2026-73658 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-73658 being exploited in the wild.
How severe is CVE-2026-73658?: High severity, with a CVSS score of 8.2, published 13 August 2026.
Which products and versions are affected?: Trigger.dev 4.4.2 to 4.5.0-rc.4.
Is there a fix for CVE-2026-73658?: A patch was published on 2026-06-05: Fix merged in PR #3830, released in version 4.5.0-rc.5 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-73658 attacked?: It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-73658?: 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.

Technical details

The vulnerability exists in Aws4FetchClient.buildUrl() and Aws4FetchClient.presign() within apps/webapp/app/v3/objectStoreClient.server.ts, which construct object-store keys from user-controlled packet parameters without validation. The presign API endpoint (apps/webapp/app/routes/api.v1.packets.$.ts) accepts arbitrary path segments via params["*"] without rejecting dot segments (..) or validating per-resource ownership. Due to WHATWG path normalization collapsing ".." segments after URL construction but before signing, an attacker with a valid environment API key could craft presigned URLs for another tenant's keys. The fix adds assertSafePacketRelativePath() validation that rejects empty paths, leading slashes, backslashes, empty segments, and traversal operators before key construction, ensuring consistent behavior across storage backends.

Affected products

Trigger.dev Trigger.dev 4.4.2 to 4.5.0-rc.4

Timeline

2026-08-13: disclosed
2026-06-05: patched: Fix merged in PR #3830, released in version 4.5.0-rc.5

References

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