Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-qxpp-qjg8-x4jv

Trigger.dev: Run replay injects a task run into an attacker-chosen environment (cross-tenant write)

CVSS 8.4 HighEPSS 0.0049 · 42nd percentile

Published by the GitHub Advisory Database at 2 Oct 2026, 19:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
trigger.devnpm<4.5.24.5.2
Identifiers
GHSA-qxpp-qjg8-x4jv · CVE-2026-85651
Weakness (CWE)
CWE-639 · CWE-862
Tags
Published
2 Oct 2026
Updated
2 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Trigger.dev versions before 4.5.2 (npm package trigger.dev) let an authenticated user replay their own run into an environment belonging to another organization or project. The replay action checks ownership of the source run but takes the target environment ID from the request without checking membership, so the attacker needs to know a target environment ID and an existing task identifier there. A successful replay creates a run in the victim's environment, using their queue and compute. Upgrade to version 4.5.2, which is the fixed version.

Written 31 Oct 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.4 High 4.0 CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:L/SC:N/SI:H/SA:L CNA (VulnCheck)
  • CISA KEV Not listed.
  • EPSS 0.0049, the 42nd percentile, on 15 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 13:34 UTC First seen by agentprime
  2. 31 Oct 2026, 13:34 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.