Read the docs
TI-2026-78690 Aliases CVE-2026-114077

Authorization bypass in Trigger.dev lets attackers hijack deployments

Priority MEDIUM 60CWE-639Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
None
Attack complexity
High
Attack requirements
Present
Impact type
Security bypass
Confidentiality · integrity · availability
Low · High · High
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.6 contains an authorization bypass in createDeploymentBackgroundWorkerV4, which looks up a WorkerDeployment by its friendlyId alone without scoping it to the environment, project, or organization. An attacker holding only their own environment API key can post a victim's deployment ID to the deployment background-workers endpoint and re-point that in-progress deployment at a worker in the attacker's environment (CWE-639). The CVSS 4.0 vector indicates a remote attacker with low privileges and no user interaction can compromise integrity and availability.

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

Description from the CNA

Trigger.dev before 4.5.6 contains an authorization bypass vulnerability in createDeploymentBackgroundWorkerV4 that resolves a WorkerDeployment by friendlyId alone, without environment, project, or organization scoping. Attackers holding only their own environment API key can POST to the deployment background-workers endpoint with a victim's deployment ID to re-point that in-progress deployment at a worker in the attacker's environment.

Why it matters now

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

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.64.5.6Patch availableCNA
  • trigger.dev Vendortriggerdotdev Affected before 4.5.6 Fixed in 4.5.6 Patch available CNA

Remediation

Trigger.dev users should upgrade to version 4.5.6 or later, which fixes the flaw. The sources list no advisory identifier for this fix.

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

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

Fixed in the same release

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

  • Release ·

    triggerdotdev trigger.dev 4.5.6

    7 records Highest priority Priority HIGH 4 HIGH, 3 MEDIUM

    Other records, highest priority first

    • TI-2026-78700 Hardcoded default secrets in Trigger.dev enable authentication bypassPriority HIGH 75
    • TI-2026-78697 SQL injection via tags in Trigger.dev Realtime Runs APIPriority HIGH 69
    • TI-2026-78694 SQL injection in Trigger.dev TSQL compiler exposes other tenants' dataPriority HIGH 69

Timeline

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

References

  • 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