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

Advisory record · `GHSA-pp95-gc86-jq6q`

- **Identifiers:** `GHSA-pp95-gc86-jq6q`
- **State:** Confirmed
- **Severity:** CVSS 7.1 High
- **Critical:** No
- **Weakness (CWE):** [CWE-862](https://cwe.mitre.org/data/definitions/862.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 2 Oct 2026
- **Updated:** 21 Oct 2026
- **Reviewed by a person:** No

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

## Affected packages

- `trigger.dev` (npm): affected `<4.5.2`; fixed in `4.5.2`

## Machine-written summary

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

> The Trigger.dev webapp (npm package trigger.dev, versions before 4.5.2) has a missing authorization check in its run replay action, which accepts POST requests without verifying the caller's identity or organization. Any authenticated user who knows a task run's friendlyId can replay that run in another organization, executing it with that organization's environment variables and secrets. The advisory also reports the same missing check on a batch completion endpoint. Upgrade to trigger.dev 4.5.2 or later.

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

- 7.1 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** No score.

## Timeline

- 31 Oct 2026, 13:33 UTC: First seen by agentprime
- 31 Oct 2026, 13:33 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-pp95-gc86-jq6q)

## Sources

- [GitHub Advisory Database: GHSA-pp95-gc86-jq6q](https://github.com/advisories/GHSA-pp95-gc86-jq6q)
- [OSV: GHSA-pp95-gc86-jq6q](https://osv.dev/vulnerability/GHSA-pp95-gc86-jq6q)
- <https://github.com/triggerdotdev/trigger.dev/security/advisories/GHSA-pp95-gc86-jq6q>
- <https://github.com/triggerdotdev/trigger.dev/pull/4199>
- <https://github.com/triggerdotdev/trigger.dev/commit/34b1a181c2a1d33a53ebab88f84b05f81fea4254>
- <https://github.com/triggerdotdev/trigger.dev>
- <https://github.com/triggerdotdev/trigger.dev/releases/tag/v4.5.2>

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.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-pp95-gc86-jq6q>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-pp95-gc86-jq6q/>. Everything for agents: <https://agentprime.io/llms.txt>.