ZDF
Sign inSign up

Vulnerabilities

Security incident · GHSA-pp95-gc86-jq6q

Trigger.dev: Missing Authentication in Run Replay Action Allows Cross-Organization Task Execution (IDOR)

Published Oct 2, 2026 · catalog updated Oct 21, 2026 · Trigger.dev: Missing Authentication in

Open the advisory

Exploitation likelihood is not on this record for GHSA-pp95-gc86-jq6q. A missing EPSS score is not a low risk. Compare Trigger.dev: Missing Authentication in with the linked advisory before you change production.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Trigger.dev: Missing Authentication in).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
  • EPSS is missing. A missing score is not a low risk.
Severity
High7.1
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
Awaiting synchronization with FIRST
Remediation
Advisory link
Affected products
npm trigger.dev

### Summary The run replay function at has no authentication or authorization check. While the (GET) in the same file properly calls and scopes queries to the user's organizations, the (POST) at line 166 does neither — allowing any authenticated user to replay task runs from any organization by knowing the run's . ### Details **Vulnerable file:** **The (line 28-29) — properly authenticated:** **The (line 166-193) — NO authentication:** The Prisma query at line 177 fetches the run by only — no or organization filter. The then creates a new task run in the victim's environment, executing with the victim's environment variables and secrets. **Same bug class exists in:** (line 17) — the has zero authentication, allowing any user to trigger batch completion for any batch ID. ### PoC **Run replay IDOR:** The values (e.g., ) are short, incrementing strings that can be enumerated. **Batch completion (same bug class):** ### Impact - **Cross-organization task execution:** An attacker can replay task runs belonging to other organizations, executing tasks in the victim's environment with the victim's secrets and API keys - **Secret exposure:** Replayed tasks run with the victim organization's environment variables, which may contain database credentials, API keys, and other secrets - **Resource consumption:** Attacker consumes the victim's compute quota by replaying their tasks - **Data integrity:** The batch completion endpoint can prematurely resume parent tasks waiting for batch results, causing data integrity issues - **Low attack complexity:** values are short, predictable strings — enumeration is feasible

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • npm trigger.dev0 → 4.5.2

How to fix GHSA-pp95-gc86-jq6q

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

Exploitation likelihood is not on this record for GHSA-pp95-gc86-jq6q. A missing EPSS score is not a low risk. Compare Trigger.dev: Missing Authentication in with the linked advisory before you change production.

Which versions are affected?

Compare what you have installed with 0 → 4.5.2. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-862: Missing Authorization. EPSS is not on this record yet. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 2, 2026 · GitHub Advisory Database

    Detected

    ### Summary The run replay function at has no authentication or authorization check. While the (GET) in the same file properly calls and scopes queries to the user's organizations, the (POST) at line 166 does neither — allowing any authenticated user to replay task runs from any organization by knowing the run's . ### Details **Vulnerable file:** **The (line 28-29) — properly authenticated:** **Th

  2. Oct 21, 2026 · GitHub Advisory Database

    Fix available

    trigger.dev fixed in 4.5.2

  3. Oct 21, 2026 · GitHub Advisory Database

    Fix available

    trigger.dev fixed in 4.5.2

  4. Oct 21, 2026 · GitHub Advisory Database

    Updated

    ### Summary The run replay function at has no authentication or authorization check. While the (GET) in the same file properly calls and scopes queries to the user's organizations, the (POST) at line 166 does neither — allowing any authenticated user to replay task runs from any organization by knowing the run's . ### Details **Vulnerable file:** **The (line 28-29) — properly authenticated:** **Th

Sources

References

Freshness

Last verified in this catalog Oct 21, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.