Is This vulnerability exploited in the wild?

No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.

How severe is This vulnerability?

Critical severity, published 2 October 2026.

Which products and versions are affected?

trigger.dev (npm) < 4.5.4; Trigger.dev before 4.5.4.

How is This vulnerability attacked?

It is attacked over the network, in a web application.

Check whether you run trigger.dev (npm) or Trigger.dev at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Trigger.dev V1 coordinator default-secret unauthenticated access

Q: Which products and versions are affected?

trigger.dev (npm) < 4.5.4; Trigger.dev before 4.5.4.

Q: Is there a fix for This vulnerability?

Yes: fixed in 4.5.4. Until then: Upgrade to v4.5.4 or later immediately. For versions before 4.5.4, operators running self-hosted instances should set non-default COORDINATOR_SECRET and PROVIDER_SECRET environment variables and restrict network access to the web application until patched. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is This vulnerability attacked?

It is attacked over the network, in a web application.

Q: Am I affected?

Check whether you run trigger.dev (npm) or Trigger.dev at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Severity: critical · Published 2026-10-02

Trigger.dev is a workflow automation platform. Self-hosted instances before version 4.5.4 shipped with hardcoded default authentication credentials for an internal Socket.IO coordinator service that were not documented, allowing unauthenticated remote attackers to connect and extract decrypted environment variables (API keys, database credentials, secrets) from any workflow run. Attackers could also forge workflow completion messages to manipulate execution state.

Technologies: trigger.dev (npm), Trigger.dev. Vendors: npm, Trigger.dev.

Quick answers

Is This vulnerability exploited in the wild?: No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
How severe is This vulnerability?: Critical severity, published 2 October 2026.
Which products and versions are affected?: trigger.dev (npm) < 4.5.4; Trigger.dev before 4.5.4.
Is there a fix for This vulnerability?: Yes: fixed in 4.5.4. Until then: Upgrade to v4.5.4 or later immediately. For versions before 4.5.4, operators running self-hosted instances should set non-default COORDINATOR_SECRET and PROVIDER_SECRET environment variables and restrict network access to the web application until patched. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is This vulnerability attacked?: It is attacked over the network, in a web application.
Am I affected?: Check whether you run trigger.dev (npm) or Trigger.dev at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: 4.5.4

Upgrade to v4.5.4 or later immediately. For versions before 4.5.4, operators running self-hosted instances should set non-default COORDINATOR_SECRET and PROVIDER_SECRET environment variables and restrict network access to the web application until patched.

Technical details

Three chained vulnerabilities enable unauthenticated access and secret exfiltration: (1) hardcoded default secrets ("coordinator-secret", "provider-secret") in source code and used for Socket.IO namespace authentication without proper override documentation, (2) the READY_FOR_EXECUTION handler returns decrypted environment variables from any run when queried by runId, regardless of tenant ownership, and (3) other coordinator handlers accept attacker-controlled writes (task completion, worker creation) without authorization checks on the runId or attemptId. The READY_FOR_EXECUTION handler only affects Run Engine 1.0 deployments; write handlers (task manipulation) affect all versions. Requires network access to the self-hosted web application.

Affected products

Trigger.dev Trigger.dev before 4.5.4

Timeline

2026-10-02: disclosed

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.