CVE-2026-73659
Path traversal in Trigger.dev allows cross-organization read/overwrite of offloaded task data.
Is CVE-2026-73659 being exploited?
Not confirmed. CVE-2026-73659 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.42% probability of exploitation in the next 30 days.
How severe is CVE-2026-73659?
CVE-2026-73659 is rated High with a CVSS score of 8.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-73659?
Yes. A fix has been recorded for CVE-2026-73659. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-73659 affect?
CVE-2026-73659 affects Trigger.dev self-hosted versions < 4.5.0 (from 4.4.2 until 4.5.0). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-73659?
Upgrade to Trigger.dev v4.5.0, rotate API keys, and audit object store access.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attackers with a project API key can traverse object-store paths to read or overwrite another org's offloaded task payloads/outputs on multi-org self-hosted instances.
Immediate action required
- affected>= 4.4.2 and < 4.5.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.