CVE-2026-73658
Path normalization flaw lets API key obtain presigned URLs for other tenants' object-store keys.
Is CVE-2026-73658 being exploited?
Not confirmed. CVE-2026-73658 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.41% probability of exploitation in the next 30 days.
How severe is CVE-2026-73658?
CVE-2026-73658 is rated High with a CVSS score of 8.2. 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-73658?
Yes. A fix has been recorded for CVE-2026-73658. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-73658 affect?
CVE-2026-73658 affects Trigger.dev webapp <= 4.5.0-rc.5, Aws4FetchClient.buildUrl/presign, apps/webapp/app/routes/api.v1.packets.$.ts. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-73658?
Upgrade to >=4.5.0-rc.5, rotate environment API keys, and audit object-store access.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
With a valid environment API key, an attacker can get presigned URLs for another tenant's objects, allowing read and overwrite of task payloads and data exfiltration.
Patch when possible
- affected>= 4.4.2 and < 4.5.0-rc.5
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.