CVE-2026-114068: Trigger.dev before 4.6.0 Missing Authorization via Waitpoint Token Wait Endpoint
triggerdotdev · trigger.dev
Fixed in 4.6.0 · Affected: triggerdotdev trigger.dev before 4.6.0 · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 30% of scored CVEs
DescriptionCVE.org
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.
Affected products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- triggerdotdev · trigger.devbefore 4.6.0
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Weakness
- Insecure Direct Object Reference
- Vendor
- triggerdotdev
- Published
- October 2026
CoverageNo articles yet
No CyberSIXT article names CVE-2026-114068 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.