CVE-2026-73654
Prototype-pollution in Trigger.dev API enables cross-tenant DoS and auth corruption.
Is CVE-2026-73654 being exploited?
Not confirmed. CVE-2026-73654 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.33% probability of exploitation in the next 30 days.
How severe is CVE-2026-73654?
CVE-2026-73654 is rated High. 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-73654?
Yes. A fix has been recorded for CVE-2026-73654. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-73654 affect?
CVE-2026-73654 affects Trigger.dev versions 3.3.8–4.5.5, PUT /api/v1/runs/:runId/metadata endpoint, Shared/self-hosted Trigger.dev webapp processes. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-73654?
Upgrade to Trigger.dev v4.5.6+, validate/whitelist operation.key, rotate API keys.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attacker with a normal API key can pollute Object.prototype, corrupt Prisma queries and Prometheus labels, break tenant auth, and cause process-wide DoS.
Immediate action required
- affected>= 3.3.8 and < 4.5.6
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.