Threats affecting pkg:github/triggerdotdev/trigger.dev

Trigger.dev versions prior to 4.5.6 contain a cross-site request forgery (CSRF) vulnerability that allows remote attackers to log out authenticated users by tricking them into clicking a specially crafted GET request to the /logout endpoint. This results in session termination and potential loss of unsaved work.

Trigger.dev versions before 4.5.0 have a vulnerability in the dashboard run replay route where no authentication or organization check is performed. This allows an attacker who knows a victim's run friendlyId to replay the run, potentially exposing sensitive task payloads or executing tasks with the victim's secrets.

Trigger.dev versions prior to 4.5.0 contain an authorization bypass vulnerability in the replay route. The system looks up runs by friendlyId without restricting the lookup to the caller's runtime environment. This allows an attacker with any tenant's API key and knowledge of a victim's run friendlyId to replay that run in their own environment and access the victim's task payload.

Trigger.dev versions before 4.5.2 contain a cross-site request forgery (CSRF) vulnerability in the CLI authorization-code flow. This flaw allows attackers to mint a Personal Access Token (PAT) without user consent by exploiting the /account/authorization-code/<code> endpoint. An attacker can lure a logged-in user to a crafted URL, then retrieve the victim's PAT from an unauthenticated endpoint, potentially leading to account takeover.

Trigger.dev versions prior to 4.5.4 contain a vulnerability due to a hardcoded default secret in the /coordinator Socket.IO namespace. This flaw allows unauthenticated attackers to connect using the known coordinator-secret, enabling them to emit events that can retrieve decrypted environment variables or tamper with task runs.

Trigger.dev versions before 4.5.6 deployed via self-hosted Docker Compose with default secrets allow authentication bypass due to a hardcoded MAGIC_LINK_SECRET. This enables unauthenticated attackers to forge valid magic link tokens, log in as any email address, and access backend services like Postgres, Redis, and ClickHouse using default credentials, compromising all tenant data.

Trigger.dev versions before 4.5.5 have a missing authentication vulnerability in the realtime streams POST handler. This flaw allows unauthenticated attackers to inject arbitrary data into any environment's realtime stream by sending POST requests with a predictable run friendlyId. The vulnerability affects all versions from 0 up to but not including 4.5.5 and has been fixed in version 4.5.5.

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.

Trigger.dev versions prior to 4.5.6 contain an SQL injection vulnerability in the /realtime/v1/runs endpoint. This flaw allows authenticated attackers with any project API key having read:runs scope to manipulate the tags query parameter, bypass tenant isolation, and access TaskRun records including payloads and metadata from all organizations on the same self-hosted instance. The vulnerability is fixed in version 4.5.6.

Trigger.dev versions before 4.5.0-rc.3 have a path traversal vulnerability in the api/v1/packets and api/v2/packets endpoints. Authenticated tenants can exploit this flaw by using unsanitized filename splat segments with '../' sequences to escape their object key prefix. This allows them to obtain presigned GET or PUT URLs and potentially read or overwrite other tenants' run payloads and outputs.

Trigger.dev versions before 4.6.2 have an authorization vulnerability that allows users with session write access and a public token to obtain environment-wide S2 stream credentials. These credentials can be used to manipulate session and run streams, including appending, creating, trimming, forging output, or deleting records. The vulnerability is fixed in version 4.6.2.

Trigger.dev versions prior to 4.5.6 contain an SQL injection vulnerability in the TSQL query compiler. This flaw allows authenticated users to inject raw subqueries via a backtick-quoted identifier in the POST /api/v1/query endpoint, bypassing tenant isolation and potentially exfiltrating analytics data from other organizations. The vulnerability is fixed in version 4.5.6.

Trigger.dev before 4.5.2 contains a blind server-side request forgery vulnerability that allows authenticated project members to make the server send requests by setting unvalidated alert-channel webhook URLs. Attackers can create alert channels pointing to loopback, internal, or cloud metadata addresses, then trigger alerts to probe internal service reachability and send signed POST requests.

Trigger.dev versions prior to 4.5.6 have an authorization bypass vulnerability that allows users with lower-trust environment API keys (such as dev, preview, or CI keys) to cancel deployments in other environments within the same project. This occurs because the DeploymentService.getDeployment method scopes lookups only by projectId, not by environment or key trust level. The issue is fixed in version 4.5.6.

Trigger.dev versions prior to 4.5.6 have an authorization bypass vulnerability in the DeleteTaskScheduleService and SetActiveOnTaskScheduleService components. This flaw allows authenticated users to delete or disable schedules belonging to other organizations by exploiting user-controlled keys. Attackers can misuse their own project's schedule route with a victim's schedule friendlyId to manipulate and destroy other organizations' imperative cron schedules.

Trigger.dev versions before 4.5.6 have an authorization bypass vulnerability in the createDeploymentBackgroundWorkerV4 function. This flaw allows attackers with their own environment API key to manipulate in-progress deployments of other users by referencing deployment IDs without proper scoping to environment, project, or organization. The vulnerability is fixed in version 4.5.6.

Trigger.dev versions before 4.5.2 have a blind server-side request forgery (SSRF) vulnerability. Authenticated tenants can exploit this by setting an unvalidated webhook alert channel URL, causing the server to send POST requests to internal hosts. This can be used to interact with internal services or cloud metadata endpoints, potentially triggering state changes or accessing IMDSv1 via redirects. The vulnerability is fixed in version 4.5.2.

Trigger.dev before 4.5.12 contains an authorization bypass vulnerability that allows holders of capability-restricted user-actor tokens to create alert channels by using the legacy personal access token helper. Attackers with a read-only UAT can POST to the project alertChannels endpoint to create production webhook channels, routing future deployment and error alerts to attacker-controlled infrastructure.

Trigger.dev versions prior to 4.5.10 contain a server-side request forgery (SSRF) vulnerability that allows authenticated project members to bypass webhook SSRF protections by targeting the 198.18.0.0/15 benchmarking IP range. This enables attackers to perform blind internal probing and limited state-changing POST requests to internally routed services within this range.

Trigger.dev CLI versions before 4.5.9 have an information disclosure vulnerability where resolved environment secret values are exposed in debug deployment logs. This occurs because unredacted environment variables are serialized into logs, potentially revealing sensitive data such as database connection strings and service credentials. Attackers who can access terminal transcripts, CI debug logs, or support bundles may exploit this to obtain confidential information.