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-114092 Overview
CVE-2026-114092 is a missing authentication vulnerability in Trigger.dev versions prior to 4.5.0. The dashboard run replay route (resources.taskruns.$runParam.replay) performs no authentication or organization check in its action handler. The handler looks up the run by friendlyId alone, with no verification that the requester owns or belongs to the run's organization.
A remote attacker who knows a victim's run friendlyId can replay that run into an environment of their choosing. This exposes the victim's task payload or re-executes the task using the victim's secrets. The weakness is classified as Missing Authentication for Critical Function [CWE-306].
Critical Impact
Unauthenticated remote attackers can replay another organization's background task runs, exposing sensitive payloads and abusing the victim's stored secrets.
Affected Products
- Trigger.dev versions prior to 4.5.0
- Self-hosted Trigger.dev dashboard deployments exposed to untrusted networks
- Trigger.dev cloud tenants running affected dashboard builds
Discovery Timeline
- 2026-10-21 - CVE-2026-114092 published to the National Vulnerability Database (NVD)
- 2026-10-22 - Last updated in NVD database
Technical Details for CVE-2026-114092
Vulnerability Analysis
Trigger.dev is an open-source background job and workflow platform. The dashboard exposes a replay action that allows users to re-run a previously executed task. In affected versions, the server action for the replay route resolves the target run using only the friendlyId path parameter and does not validate that the authenticated session belongs to the owning organization.
Because the handler is reachable without authentication context enforcement, an attacker who obtains or guesses a friendlyId can submit a replay request and redirect the execution to an environment they control. The replayed run carries the original task payload and executes with the victim's configured secrets. The result is both confidentiality loss on the input data and unauthorized use of production credentials bound to the task.
Root Cause
The root cause is a missing authorization check in the action handler for resources.taskruns.$runParam.replay. The code path trusts the friendlyId lookup as sufficient to identify an authorized request, omitting any session, user, or organization membership verification before invoking the replay operation.
Attack Vector
The vulnerability is exploitable over the network with low attack complexity and no privileges or user interaction required. The attacker must know the target run's friendlyId. These identifiers are passed in URLs, logs, and webhook payloads, which increases the practical disclosure risk in shared tooling or multi-tenant integrations.
Technical details are documented in the GitHub Security Advisory GHSA-9fq3-68cw-r7p2, the related advisory GHSA-pp95-gc86-jq6q, and the VulnCheck advisory on the missing authentication issue.
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-114092
Indicators of Compromise
- Replay requests to /resources/taskruns/<friendlyId>/replay originating from unexpected IP addresses or user agents.
- Task runs executing in environments that do not match the environment of the original run.
- Unexplained duplicate executions of production tasks or spikes in replay activity for high-value jobs.
- Audit log entries showing replay actions with no associated authenticated user or session context.
Detection Strategies
- Review Trigger.dev dashboard access logs for POST requests to the replay route that lack valid session cookies or authentication headers.
- Correlate replay events with the originating organization ID of the referenced run and flag mismatches.
- Alert on replays that change the destination environment relative to the source run.
Monitoring Recommendations
- Forward Trigger.dev application and reverse proxy logs to a centralized logging platform for retention and search.
- Baseline normal replay volumes per organization and environment, then alert on deviations.
- Monitor outbound traffic from workers for connections to unexpected destinations following replay events, which may indicate secret abuse.
How to Mitigate CVE-2026-114092
Immediate Actions Required
- Upgrade all Trigger.dev dashboard and worker components to version 4.5.0 or later.
- Rotate any API keys, tokens, and secrets referenced by task runs that may have been replayed by an unauthorized party.
- Audit replay activity in the dashboard and application logs since the dashboard became reachable.
- Restrict dashboard network exposure to trusted networks or an authenticated reverse proxy until patching completes.
Patch Information
The issue is fixed in Trigger.dev 4.5.0. The patched action handler enforces authentication and verifies that the requesting user belongs to the organization owning the referenced run before performing the replay. Refer to the GitHub Security Advisory GHSA-9fq3-68cw-r7p2 and GHSA-pp95-gc86-jq6q for upgrade guidance.
Workarounds
- Place the Trigger.dev dashboard behind a reverse proxy or VPN that enforces authentication at the network edge.
- Block external access to paths matching /resources/taskruns/*/replay at the proxy or WAF layer until the upgrade is applied.
- Treat run friendlyId values as sensitive and avoid including them in external logs, support tickets, or third-party integrations.
# Example NGINX restriction for the replay route until upgrade
location ~ ^/resources/taskruns/[^/]+/replay$ {
allow 10.0.0.0/8;
deny all;
proxy_pass http://trigger_dashboard_upstream;
}
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

