CVE-2026-114085 in Trigger.dev
Summary
by MITRE • 10/21/2026
Trigger.dev through 4.7.6 contains a missing authentication vulnerability in the supervisor workload server that allows workloads to manipulate runs belonging to other deployments without ownership verification. Attackers with network access and a valid run/snapshot pair can call the attempts/start endpoint to obtain resolved environment variables and run JWTs, or start, complete, and suspend other tenants' runs.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Analysis
by VulDB Data Team • 10/21/2026
The vulnerability identified in Trigger.dev versions through 4.7.6 represents a critical failure in identity verification within the supervisor workload server architecture. This flaw specifically affects how workloads interact with the central orchestration layer that manages execution states. The core technical deficiency lies in the absence of ownership validation when processing requests to manipulate run lifecycles. In a properly secured multi-tenant environment, any operation targeting a specific job or workflow instance must verify that the requesting entity possesses valid authorization for that particular resource ID. However, in this implementation, the endpoint responsible for initiating attempts lacks these necessary checks, allowing authenticated users or processes with network access to target arbitrary run identifiers without proving ownership of those runs.
From an operational perspective, this missing authentication mechanism enables significant lateral movement and data manipulation within the platform. An attacker who has obtained a valid pair consisting of a run identifier and its corresponding snapshot can interact directly with the attempts/start endpoint. This interaction allows the adversary to resolve sensitive environment variables associated with other deployments, effectively leaking configuration secrets that may include API keys, database credentials, or internal service tokens. Furthermore, the ability to start, complete, or suspend runs belonging to different tenants means an attacker can disrupt business continuity by halting critical processes or forge completion statuses for jobs they did not execute. This undermines the integrity of audit logs and workflow execution records, making it difficult to trace actual actions taken versus those fabricated by malicious actors.
The security implications extend beyond immediate data leakage to include potential denial-of-service conditions and state corruption. By suspending runs belonging to other tenants, an attacker can cause service outages for legitimate users who depend on timely completion of these workflows. Additionally, completing runs prematurely or incorrectly may trigger downstream actions based on false premises, such as sending notifications, updating databases, or initiating financial transactions if the workflow is part of a larger automated pipeline. The ability to obtain resolved environment variables also facilitates further exploitation by providing attackers with the contextual information needed to craft more sophisticated attacks against dependent services that trust these credentials.
This vulnerability aligns closely with CWE-287, which describes Improper Authentication, as well as CWE-306, Missing Authentication for Critical Function. In terms of attack vectors and tactics, it maps directly to MITRE ATT&CK technique T1548.001, Abuse Elevation Control Mechanism: Bypass User Interface Restrictions, where the attacker bypasses intended access controls by interacting with backend APIs rather than the user interface. It also relates to T1078, Valid Accounts, as exploitation requires some form of valid authentication or network access that grants entry into the system boundary. The scenario reflects a classic case of insecure direct object references (IDOR) where resource identifiers are exposed and manipulated without sufficient authorization checks on the server side.
Mitigation strategies must prioritize immediate patching to version 4.7.7 or later, which addresses this specific oversight in the supervisor workload server logic. Until patches are applied, organizations should implement strict network segmentation to limit access to the internal APIs used by workloads and the orchestration layer. Additionally, deploying web application firewalls with rules that detect anomalous patterns of run ID manipulation can provide a temporary defensive layer. It is also crucial to rotate any environment variables or secrets that may have been exposed during periods when this vulnerability was active in production environments. Long-term remediation should involve implementing comprehensive identity and access management policies that enforce strict ownership verification for all state-changing operations, ensuring that every API call validates the requester's relationship to the target resource before execution.