Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-114091 Overview
CVE-2026-114091 is an authorization vulnerability in Trigger.dev versions before 4.5.0. The flaw resides in the api.v1.runs.$runParam.replay route, which looks up runs by friendlyId alone 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. The replay operation discloses the victim's task payload, resulting in cross-tenant data exposure. The issue is tracked under CWE-639: Authorization Bypass Through User-Controlled Key.
Critical Impact
Any authenticated tenant can read another tenant's task payloads by replaying runs across environment boundaries.
Affected Products
- Trigger.dev versions prior to 4.5.0
- Self-hosted Trigger.dev deployments on affected versions
- Trigger.dev cloud tenants running vulnerable builds
Discovery Timeline
- 2026-10-21 - CVE CVE-2026-114091 published to NVD
- 2026-10-21 - Last updated in NVD database
Technical Details for CVE-2026-114091
Vulnerability Analysis
Trigger.dev isolates workloads using runtime environments tied to tenant-scoped API keys. The api.v1.runs.$runParam.replay endpoint accepts a friendlyId path parameter and loads the corresponding run record from the database. The handler fails to filter the query by the caller's environment identifier derived from the authenticated API key.
As a result, any valid API key authorizes replay of any run whose friendlyId is known or guessed. The replay path reconstructs the original task invocation inside the attacker's environment and returns the stored task payload. Because payloads may contain application secrets, PII, or integration tokens, the authorization bypass produces direct confidentiality loss across tenant boundaries.
Root Cause
The root cause is a missing authorization check on an object reference. The lookup predicate uses only friendlyId as the key rather than combining it with the authenticated environment or organization identifier. This pattern matches [CWE-639], where authorization decisions rely on client-supplied identifiers without validating ownership.
Attack Vector
Exploitation requires network access to the Trigger.dev API and a valid low-privilege API key for any tenant. The attacker calls the replay route with a target friendlyId belonging to a victim tenant. The server executes the replay in the attacker's environment and returns the victim's task payload. No user interaction is required. See the GitHub Security Advisory GHSA-9fq3-68cw-r7p2 and the VulnCheck Advisory for Trigger.dev for additional detail.
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2026-114091
Indicators of Compromise
- Unexpected POST requests to /api/v1/runs/{friendlyId}/replay where the friendlyId does not belong to the authenticated API key's environment.
- Replay events in audit logs that reference runs created by other organizations or projects.
- API keys issuing replay calls at higher-than-baseline rates or iterating through sequential friendlyId values.
Detection Strategies
- Correlate the friendlyId on replay requests against the owning environment and alert on mismatches.
- Baseline per-API-key access patterns to the replay route and flag deviations such as access to previously unseen run identifiers.
- Review application logs for replay operations that produced payload responses without a matching original creation event in the same environment.
Monitoring Recommendations
- Enable verbose audit logging on all /api/v1/runs/* routes, capturing API key ID, environment, and friendlyId.
- Forward Trigger.dev logs to a centralized analytics platform to retain cross-tenant visibility.
- Monitor outbound data volume from the replay endpoint to detect bulk payload extraction.
How to Mitigate CVE-2026-114091
Immediate Actions Required
- Upgrade Trigger.dev to version 4.5.0 or later on all self-hosted and managed deployments.
- Rotate all tenant API keys issued before the upgrade to invalidate credentials potentially used for probing.
- Audit historical replay activity to identify cross-environment access and notify affected tenants.
Patch Information
The maintainers resolved the vulnerability in Trigger.dev 4.5.0 by scoping the replay lookup to the caller's runtime environment. Refer to the GitHub Security Advisory GHSA-9fq3-68cw-r7p2 for the fix commits and release notes.
Workarounds
- Restrict network access to the Trigger.dev API using an authenticating reverse proxy or allowlist until the upgrade is applied.
- Disable the replay endpoint at the gateway layer if replay functionality is not required by production workloads.
- Treat all stored task payloads as potentially exposed and rotate any secrets, tokens, or credentials embedded in historical run data.
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

