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

Summary

### Summary The dashboard replay action authorizes the source run (it must belong to the caller's org), but the target environment for the replayed run is taken verbatim from the request body and is never checked for org or project membership. The environment lookup used by the replay path filters by id only. As a result, an authenticated user can replay one of their own runs into another organization's or…

Timeline

Published by source

2026-10-02

Risk context

• Reported severity or threat level: high.
• Reported CVSS score: 7.1 out of 10.
• Review exposure for the affected product or family: npm: trigger.dev.

Product

npm: trigger.dev

What to do

General, cautious steps (verify details in the official source):

• Prioritize patching or mitigation immediately (treat as actively risky).
• Identify affected product versions in your inventory and verify whether you are impacted.
• Apply vendor patches/updates or recommended mitigations as soon as available.
• Read the official advisory for exact affected versions and remediation steps.

Official advisory

• Read the official source

Evidence and provenance

Canonical advisory ID

GHSA-QXPP-QJG8-X4JV

Source

GitHub

Vendor

GitHub

Published by source

2026-10-02

Last source activity

2026-10-02

Curated by

hlukh.ch

Related advisories and connections

These advisories are connected by shared CVE, product, vendor, source, or time signals.