GHSA-pp95-gc86-jq6q: Trigger.dev Missing Authentication Vulnerability
HIGHGHSA-pp95-gc86-jq6q is a HIGH (CVSS 7.1) missing authentication vulnerability (CWE-862: Missing Authorization) affecting Trigger.dev libraries in the npm ecosystem. The issue involves missing authentication in run replay action allows cross-organization task execution (idor). Remediation is available by upgrading affected packages to version 4.5.2.
GHSA-pp95-gc86-jq6q at a Glance
Security Impact
CVSS: 7.1
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N).
How to Fix GHSA-pp95-gc86-jq6q
To remediate this vulnerability, upgrade all affected Trigger.dev dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
npm install trigger.dev@4.5.2
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
npm ls trigger.dev
How to Check if You Are Affected
To determine whether your Node.js application is affected by GHSA-pp95-gc86-jq6q, inspect your project dependencies using npm:
npm ls trigger.dev
Analyze the terminal output to locate any version of Trigger.dev in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 4.5.2), your application is affected.
Note: The npm ls trigger.dev command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-862: Missing Authorization, where the product does not perform an authorization check when an actor attempts to access a resource or perform an action. In Trigger.dev, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
GHSA-pp95-gc86-jq6q Affected Trigger.dev Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
trigger.dev
|
npm |
< 4.5.2
|
4.5.2
|
References
Frequently Asked Questions
What is GHSA-pp95-gc86-jq6q?
Which Trigger.dev versions are affected?
What version fixes GHSA-pp95-gc86-jq6q?
Is trigger.dev affected?
What is the CVSS score of GHSA-pp95-gc86-jq6q?
What CWE is associated with GHSA-pp95-gc86-jq6q?
How can I check npm dependencies for GHSA-pp95-gc86-jq6q?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-pp95-gc86-jq6q",
"modified" : "2026-10-02T22:35:24Z",
"published" : "2026-10-02T22:35:24Z",
"aliases" : [ ],
"summary" : "Trigger.dev: Missing Authentication in Run Replay Action Allows Cross-Organization Task Execution (IDOR)",
"details" : "### Summary\n\nThe run replay `action` function at `apps/webapp/app/routes/resources.taskruns.$runParam.replay.ts` has no authentication or authorization check. While the `loader` (GET) in the same file properly calls `requireUser(request)` and scopes queries to the user's organizations, the `action` (POST) at line 166 does neither — allowing any authenticated user to replay task runs from any organization by knowing the run's `friendlyId`.\n\n### Details\n\n**Vulnerable file:** `apps/webapp/app/routes/resources.taskruns.$runParam.replay.ts`\n\n**The `loader` (line 28-29) — properly authenticated:**\n```typescript\nexport async function loader({ request, params }: LoaderFunctionArgs) {\n const user = await requireUser(request); // ✓ Auth check\n const userId = user.id;\n // ... queries scoped to user's orgs\n}\n```\n\n**The `action` (line 166-193) — NO authentication:**\n```typescript\nexport const action: ActionFunction = async ({ request, params }) => {\n const { runParam } = ParamSchema.parse(params);\n // ✗ NO requireUser() call\n // ✗ NO requireUserId() call\n // ✗ NO org membership check\n\n const taskRun = await prisma.taskRun.findFirst({\n where: {\n friendlyId: runParam, // Queries ANY run, no org scoping\n },\n include: {\n runtimeEnvironment: { select: { slug: true } },\n project: { include: { organization: true } },\n },\n });\n\n // ... proceeds to replay the run in the victim's environment\n const replayRunService = new ReplayTaskRunService();\n```\n\nThe Prisma query at line 177 fetches the run by `friendlyId` only — no `userId` or organization filter. The `ReplayTaskRunService` then creates a new task run in the victim's environment, executing with the victim's environment variables and secrets.\n\n**Same bug class exists in:** `apps/webapp/app/routes/resources.batches.$batchId.check-completion.ts` (line 17) — the `action` has zero authentication, allowing any user to trigger batch completion for any batch ID.\n\n### PoC\n\n**Run replay IDOR:**\n```bash\n# Any authenticated user can replay any org's task run\nPOST /resources/taskruns/run_abc123def/replay\nCookie: <any-valid-session>\nContent-Type: application/x-www-form-urlencoded\n\nenvironmentId=<victim-env-id>&failedRedirect=/\n```\n\nThe `friendlyId` values (e.g., `run_abc123def`) are short, incrementing strings that can be enumerated.\n\n**Batch completion (same bug class):**\n```bash\n# Any authenticated user can trigger batch completion for any batch\nPOST /resources/batches/<batchId>/check-completion\nCookie: <any-valid-session>\nContent-Type: application/x-www-form-urlencoded\n\nredirectUrl=/\n```\n\n### Impact\n\n- **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\n- **Secret exposure:** Replayed tasks run with the victim organization's environment variables, which may contain database credentials, API keys, and other secrets\n- **Resource consumption:** Attacker consumes the victim's compute quota by replaying their tasks\n- **Data integrity:** The batch completion endpoint can prematurely resume parent tasks waiting for batch results, causing data integrity issues\n- **Low attack complexity:** `friendlyId` values are short, predictable strings — enumeration is feasible",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "npm",
"name" : "trigger.dev"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "4.5.2"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 4.5.1"
}
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/triggerdotdev/trigger.dev/security/advisories/GHSA-pp95-gc86-jq6q"
}, {
"type" : "WEB",
"url" : "https://github.com/triggerdotdev/trigger.dev/pull/4199"
}, {
"type" : "WEB",
"url" : "https://github.com/triggerdotdev/trigger.dev/commit/34b1a181c2a1d33a53ebab88f84b05f81fea4254"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/triggerdotdev/trigger.dev"
}, {
"type" : "WEB",
"url" : "https://github.com/triggerdotdev/trigger.dev/releases/tag/v4.5.2"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-862" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2026-10-02T22:35:24Z",
"nvd_published_at" : null
}
}