CVE-2026-85651
Received Received - Intake

Trigger.dev Environment Replay Task Injection Vulnerability

Vulnerability report for CVE-2026-85651, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-09-04

Last updated on: 2026-09-04

Assigner: VulnCheck

Description

Trigger.dev versions before 4.5.2 fail to validate environment membership during run replay operations, allowing authenticated attackers to inject task runs into arbitrary environments. Attackers can replay their own runs into other organizations' or projects' environments to consume victim resources and pollute run history.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-04
Last Modified
2026-09-04
Generated
2026-09-04
AI Q&A
2026-09-04
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
trigger.dev trigger.dev to 4.5.2 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-862 The product does not perform an authorization check when an actor attempts to access a resource or perform an action.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-85651 is a vulnerability in Trigger.dev versions before 4.5.2 where authenticated attackers can inject task runs into arbitrary environments by replaying their own runs. The system fails to validate if the target environment belongs to the attacker's organization or project, allowing unauthorized cross-tenant writes. This consumes victim resources and pollutes run history.

Detection Guidance

To detect this vulnerability, check if your Trigger.dev instance is running a version before 4.5.2. Use commands like 'npm list trigger.dev' or 'docker inspect <container_name> | grep trigger.dev' to verify the installed version. Monitor logs for unauthorized run replay attempts or unexpected task executions in environments not owned by the user.

Impact Analysis

This vulnerability allows attackers to consume your organization's queue and compute resources by injecting unauthorized task runs into your environments. It also pollutes your run history, making it harder to track legitimate operations. Exploitation requires knowing a valid environment ID and task identifier in your environment.

Compliance Impact

This vulnerability could lead to unauthorized access to environments, potentially exposing sensitive data stored or processed in those environments. For GDPR, this may result in unauthorized data processing or access, violating principles of lawfulness and integrity. For HIPAA, it could allow unauthorized access to protected health information, compromising confidentiality and integrity requirements.

Mitigation Strategies

Immediately upgrade Trigger.dev to version 4.5.2 or later. If upgrading is not possible, restrict access to the run replay feature and environment IDs. Review logs for signs of exploitation and revoke any unauthorized task runs. Ensure environment ownership validation is enforced in all replay operations.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-85651. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart