GHSA-PP95-GC86-JQ6Q

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

export async function loader({ request, params }: LoaderFunctionArgs) {
  const user = await requireUser(request);  // ✓ Auth check
  const userId = user.id;
  // ... queries scoped to user's orgs
}

export const action: ActionFunction = async ({ request, params }) => {
  const { runParam } = ParamSchema.parse(params);
  // ✗ NO requireUser() call
  // ✗ NO requireUserId() call
  // ✗ NO org membership check

  const taskRun = await prisma.taskRun.findFirst({
    where: {
      friendlyId: runParam,  // Queries ANY run, no org scoping
    },
    include: {
      runtimeEnvironment: { select: { slug: true } },
      project: { include: { organization: true } },
    },
  });

  // ... proceeds to replay the run in the victim's environment
  const replayRunService = new ReplayTaskRunService();

# Any authenticated user can replay any org's task run
POST /resources/taskruns/run_abc123def/replay
Cookie: <any-valid-session>
Content-Type: application/x-www-form-urlencoded

environmentId=<victim-env-id>&failedRedirect=/

# Any authenticated user can trigger batch completion for any batch
POST /resources/batches/<batchId>/check-completion
Cookie: <any-valid-session>
Content-Type: application/x-www-form-urlencoded

redirectUrl=/

• 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: friendlyId values are short, predictable strings, enumeration is feasible

The application does not perform an authorization check before performing a sensitive operation. Typical impact: unauthorized access to restricted functionality or data.

GHSA-PP95-GC86-JQ6Q has a CVSS score of 7.1 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (4.5.2); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

1. What is GHSA-PP95-GC86-JQ6Q? GHSA-PP95-GC86-JQ6Q is a high-severity missing authorization vulnerability in trigger.dev (npm), affecting versions <= 4.5.1. It is fixed in 4.5.2. The application does not perform an authorization check before performing a sensitive operation.
2. How severe is GHSA-PP95-GC86-JQ6Q? GHSA-PP95-GC86-JQ6Q has a CVSS score of 7.1 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of trigger.dev are affected by GHSA-PP95-GC86-JQ6Q? trigger.dev (npm) versions <= 4.5.1 is affected.
4. Is there a fix for GHSA-PP95-GC86-JQ6Q? Yes. GHSA-PP95-GC86-JQ6Q is fixed in 4.5.2. Upgrade to this version or later.
5. Is GHSA-PP95-GC86-JQ6Q exploitable, and should I be worried? Whether GHSA-PP95-GC86-JQ6Q is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether GHSA-PP95-GC86-JQ6Q is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix GHSA-PP95-GC86-JQ6Q? Upgrade trigger.dev to 4.5.2 or later.

Other vulnerabilities in trigger.dev