# CVE-2026-73659: Trigger.dev: Cross-tenant object read/write via path traversal in packet presign API

> Attackers can read or overwrite other organizations' data via path traversal in the packet presign API on multi-organization self-hosted instances.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Aug 2026
- **Updated:** 14 Aug 2026
- **Also known as:** GHSA-m3mf-37q7-8928

## What is CVE-2026-73659?

CVE-2026-73659 is a high-severity path traversal vulnerability in triggerdotdev trigger.dev, published on 13 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Trigger.dev is the open-source platform for building AI workflows in TypeScript. From 4.4.2 until 4.5.0, the packet presign routes in apps/webapp/app/routes/api.v1.packets.$.ts pass a caller-controlled filename through resolveStoreProtocolForPacketPresign to generatePresignedUrl and generatePresignedRequest in apps/webapp/app/v3/objectStore.server.ts, allowing .. traversal to escape the packets/<projectRef>/<env>/ object-store prefix and enabling a project API key to read or overwrite another organization's offloaded task payloads and outputs on multi-organization self-hosted instances. This issue is fixed in version 4.5.0.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-73659?


## How do I fix CVE-2026-73659?

No fix has been published for CVE-2026-73659 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-73659 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-73659 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-73659 and fix it if it is affected.

What it is: CVE-2026-73659 is a high-severity path traversal vulnerability in triggerdotdev trigger.dev, published on 13 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-73659 exists.

Affected product: triggerdotdev trigger.dev. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-73659/ (Markdown: https://insights.sbomify.com/CVE-2026-73659/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-73659
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-73659
- OSV: https://osv.dev/vulnerability/CVE-2026-73659

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-73659/
Summaries are generated and may contain mistakes; the official description above is the record.