Skip to main content
VulnerabilityPublished

CVE-2026-73656: triggerdotdev trigger.dev · Insecure Direct Object Reference

Affects triggerdotdev trigger.devSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.9 Critical : upgrade to 4.5.2 as a priority.

Data as of 10 Nov 2026, 23:24 UTC

CVSS 3.1 base score
9.9Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.5.2, 4.5.6
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.

What to do

Upgrade trigger.dev to 4.5.2; triggerdotdev/trigger.dev to 4.5.6.

Affected software

ProductAffectedFixed in
triggerdotdevtrigger.devAffected
  • <4.5.2
Fixed in
  • 4.5.2
GitHubtriggerdotdev/trigger.devpkg:github/triggerdotdev/trigger.devOther threatsAffected
  • <4.5.6
Fixed in
  • 4.5.6

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Trigger.dev to version 4.5.6 or later, where this authorization bypass vulnerability is fixed. No other mitigation or temporary workaround is documented. Patch status is confirmed fixed in 4.5.6.

Description

Trigger.dev versions prior to 4.5.6 contain an authorization bypass vulnerability in the background worker deployment API. The flaw allows a user with a valid API key for one project to manipulate deployment identifiers from another project, linking an attacker-controlled background worker to a victim deployment and changing its state from BUILDING to DEPLOYING. This issue is resolved in version 4.5.6.

References

Community reviews

Loading reviews…