Read the docs
TI-2026-78704 Aliases CVE-2026-114091

Authorization bypass in Trigger.dev replay route exposes run payloads

Priority MEDIUM 60CWE-639Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
None
Attack complexity
Low
Attack requirements
Present
Impact type
Security bypass
Confidentiality · integrity · availability
High · None · None
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-639.

Summary

Trigger.dev before 4.5.0 looks up runs by friendlyId alone in the api.v1.runs.$runParam.replay route, without scoping the lookup to the caller's runtime environment. An attacker holding any tenant's API key who knows a victim's run friendlyId can replay that run into their own environment and read the victim's task payload. The weakness is classified as CWE-639, authorization bypass through a user-controlled key.

Written with Claude Haiku 5.5 from the sources below · 2026-10-28

Description from the CNA

Trigger.dev before 4.5.0 looks up runs by friendlyId alone in the api.v1.runs.$runParam.replay route without scoping the lookup to the caller's runtime environment. An attacker holding any tenant's API key who knows a victim's run friendlyId can replay that run into their own environment and read the victim's task payload.

Why it matters now

Exploitation Proof of concept CISA SSVC · not in CISA KEV
EPSS 0.00339 27th percentileScored 2026-11-07
Fix Fixed trigger.dev (triggerdotdev): 4.5.0

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
Poc
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
triggerdotdevtrigger.devbefore 4.5.04.5.0Patch availableCNA
  • trigger.dev Vendortriggerdotdev Affected before 4.5.0 Fixed in 4.5.0 Patch available CNA

Remediation

Upgrade trigger.dev to version 4.5.0 or later, which fixes the issue.

Written with Claude Haiku 5.5 from the sources below · 2026-10-28

  • Fix · CNA trigger.dev (triggerdotdev) Fixed in 4.5.0

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Advisory ·

    triggerdotdev trigger.dev — GitHub Security Advisory (GHSA-9fq3-68cw-r7p2)

    2 records Highest priority Priority HIGH 1 HIGH, 1 MEDIUM

    Other records, highest priority first

    • TI-2026-78705 Missing authentication in Trigger.dev dashboard run replay actionPriority HIGH 69
    Show all 2 records → Advisory →

Timeline

  1. 2026-10-21 Threatist record created from CVE-2026-114091
  2. 2026-10-22 Priority changed: MEDIUM → LOW
  3. 2026-10-28 CISA SSVC decision points changed
  4. 2026-10-28 Priority changed: LOW → MEDIUM

References

Advisory 1

  • TI-2026-78700 Hardcoded default secrets in Trigger.dev enable authentication bypass CVSS 4.0CRITICAL 9.2
  • TI-2026-78702 Cross-site request forgery in Trigger.dev CLI leads to token theft CVSS 4.0HIGH 8.7
  • TI-2026-78696 Trigger.dev Path Traversal in Packets Presigned URL Endpoints CVSS 4.0HIGH 8.6
  • TI-2026-78682 Improper authorization in Trigger.dev exposes root API key via envvars endpoint CVSS 4.0HIGH 8.6
  • TI-2026-51742 Trigger.dev: Cross-tenant object store read and write via URL path traversal CVSS 3.1HIGH 8.2
  • TI-2026-78699 Trigger.dev realtime streams accept unauthenticated data injection CVSS 4.0MEDIUM 6.9
See all 36 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences