CVE-2026-114068Trigger.dev before 4.6.0 Missing Authorization via Waitpoint Token Wait Endpoint
Updated under an hour ago ()
Does this affect you?
It affects triggerdotdev trigger.dev. Add what you run to find out whether that includes you.
EPSS puts the chance of exploitation in the next 30 days at 0.25%, higher than 16% of scored CVEs.
Do this next
Free account, 1 product
Trigger.dev before 4.6.0 contains a missing authorization vulnerability in the waitpoint token wait endpoint that allows authenticated attackers to block runs belonging to other organizations. Attackers holding any secret API key can supply a victim run ID with their own waitpoint, causing that run to block indefinitely on a waitpoint the victim cannot complete, and can inject resume data into it.
- CVSS
- 8.3 HIGH (v3.1, CNA)CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:H
- Weakness (CWE)
- CWE-639
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- 0.25% (percentile 16)
- Assigned by
- VulnCheck
- NVD analysis
- Deferred
- Record last updated
- Oct 21, 2026
- First seen by InfoSec Signals
- Oct 21, 2026
Affected products
triggerdotdev trigger.dev triggerdotdev:trigger.dev (from the name) | before 4.6.0; 4.6.0 not affected | CNA record |
References
- https://github.com/triggerdotdev/trigger.dev/security/advisories/GHSA-xrp6-5fpv-4fxfvendor-advisory
- https://www.vulncheck.com/advisories/trigger-dev-before-4.6.0-missing-authorization-via-waitpoint-token-wait-endpointthird-party-advisory
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.