Trigger.dev: Cross-environment deployment cancel — GHSA-4672-HWV6-GQ62

Summary

### Summary Trigger.dev isolates each project into multiple **environments** (`dev`, `staging`, `prod`, and per-PR `preview` branches), each with its **own secret API key** — the environment is a trust boundary (a `dev`/preview/CI key is lower-trust than a `prod` key). Most API routes enforce this by scoping resource lookups to the authenticated key's environment (`where: { friendlyId, runtimeEnvironmentId:…

Timeline

Published by source

2026-10-02

Risk context

• Reported severity or threat level: medium.
• Reported CVSS score: 5.4 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):

• Review exposure and plan remediation based on risk and environment.
• 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-4672-HWV6-GQ62

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.