CVE-2026-85651: Trigger.dev Auth Bypass Vulnerability

CVE-2026-85651 Overview

CVE-2026-85651 is a missing authorization vulnerability [CWE-862] in Trigger.dev versions before 4.5.2. The platform fails to validate environment membership during run replay operations. Authenticated attackers can inject task runs into environments belonging to other organizations or projects. This allows adversaries to consume victim compute resources and pollute run history with unauthorized executions.

Critical Impact
Authenticated attackers can replay their own task runs into arbitrary environments across tenant boundaries, breaking multi-tenant isolation and enabling resource abuse against other organizations.

Affected Products

Trigger.dev versions prior to 4.5.2
Self-hosted Trigger.dev deployments running affected versions
Trigger.dev Cloud environments prior to the patched release

Discovery Timeline

2026-09-04 - CVE-2026-85651 published to NVD
2026-09-10 - Last updated in NVD database

Technical Details for CVE-2026-85651

Vulnerability Analysis

Trigger.dev is an open-source background jobs and workflow platform. The application organizes work into organizations, projects, and environments. The run replay feature allows users to re-execute a previous task run using its identifier.

Before version 4.5.2, the replay endpoint did not enforce that the caller belonged to the target environment. An authenticated user could reference a run identifier and replay it into an environment they did not own. The server accepted the request based on authentication alone, without verifying membership of the destination environment.

The result is a cross-tenant execution primitive. Attackers can queue workloads into victim environments, causing resource consumption on victim infrastructure and injecting spurious entries into their run history.

Root Cause

The root cause is missing authorization [CWE-862] on the run replay code path. Environment membership was not validated against the authenticated principal before scheduling the replayed run. The permission check assumed that possession of a run identifier implied legitimate access to the target environment.

Attack Vector

An attacker requires a valid Trigger.dev account. Using their own run as a source, the attacker submits a replay request that targets an environment identifier belonging to another organization or project. The server processes the request and enqueues the run in the victim environment.

typescript

// Illustrative patch context from the Trigger.dev security release
// Source: https://github.com/triggerdotdev/trigger.dev/commit/34b1a181c2a1d33a53ebab88f84b05f81fea4254

// The security release added scoped lookups that bind target objects
// to the caller's resolved organization, rejecting foreign identifiers:
//
//   const member = await prisma.orgMember.findFirst({
//     where: { id: memberId, organizationId: org.id },
//     ...
//   });
//
// Equivalent scoping was applied to run replay so that the destination
// environment must belong to an organization the caller is a member of.

Source: GitHub Commit 34b1a181

Detection Methods for CVE-2026-85651

Indicators of Compromise

Task runs in an environment whose triggeredBy user is not a member of the owning organization or project
Unexplained spikes in run volume or compute usage that do not correlate with legitimate workflow schedules
Replay events in application logs where the source run identifier resolves to a different organization than the destination environment

Detection Strategies

Query the Trigger.dev database for runs where the creator's organization membership does not match the environment's organization
Correlate replay API calls with the authenticated user's environment membership and flag mismatches
Baseline expected replay volume per environment and alert on statistical deviations

Monitoring Recommendations

Enable audit logging on the replay endpoint and forward events to a centralized log platform for analysis
Monitor billing and compute telemetry per environment for cost anomalies indicative of injected workloads
Track failed authorization decisions after upgrading to 4.5.2 to identify attempted cross-tenant replays

How to Mitigate CVE-2026-85651

Immediate Actions Required

Upgrade Trigger.dev to version 4.5.2 or later without delay, following the GitHub Release v4.5.2 notes
Review recent run history for entries triggered by users outside the owning organization and remove unauthorized runs
Rotate API keys and session tokens if unauthorized replay activity is confirmed

Patch Information

The fix is delivered in Trigger.dev 4.5.2. Details are published in GitHub Security Advisory GHSA-qxpp-qjg8-x4jv and tracked in GitHub Issue #4173. Additional context is available in the VulnCheck Advisory on Trigger.dev.

Workarounds

Restrict Trigger.dev account creation to trusted users until the upgrade is applied, reducing the pool of authenticated attackers
Place the Trigger.dev web application behind network controls that limit access to known operators
Increase log retention and alerting on the replay endpoint to detect abuse pending remediation

bash

# Upgrade self-hosted Trigger.dev to the patched release
git fetch --tags
git checkout v4.5.2

# Rebuild and redeploy the affected services
pnpm install
pnpm run build
docker compose up -d --build