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?

Medium severity, with a CVSS score of 5.4, published 2 October 2026.

Which products and versions are affected?

trigger.dev (npm) <= 4.5.1; Trigger.dev 5d99457 (HEAD/main).

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 blind server-side request forgery via webhook URL

Q: Which products and versions are affected?

trigger.dev (npm) <= 4.5.1; Trigger.dev 5d99457 (HEAD/main).

Q: Is there a fix for This vulnerability?

No fixed version is recorded yet. Validate webhook URLs at creation time and again at delivery time: require http(s) scheme, resolve the hostname, and reject any URL that resolves to a private/link-local/loopback/metadata IP range. Consider disabling redirects in the fetch call or re-validating the resolved IP after redirects. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

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: medium · CVSS 5.4 · Published 2026-10-02

Trigger.dev is a workflow orchestration platform that allows authenticated users to configure webhook alert channels. An attacker with authenticated access can set a webhook URL to an internal server (such as cloud metadata endpoints like 169.254.169.254) and trigger alerts that cause the Trigger.dev server to make HTTP requests to that internal URL. This enables internal network scanning, state-changing requests to internal services, and potential credential theft from cloud metadata endpoints.

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?: Medium severity, with a CVSS score of 5.4, published 2 October 2026.
Which products and versions are affected?: trigger.dev (npm) <= 4.5.1; Trigger.dev 5d99457 (HEAD/main).
Is there a fix for This vulnerability?: No fixed version is recorded yet. Validate webhook URLs at creation time and again at delivery time: require http(s) scheme, resolve the hostname, and reject any URL that resolves to a private/link-local/loopback/metadata IP range. Consider disabling redirects in the fetch call or re-validating the resolved IP after redirects. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
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

Validate webhook URLs at creation time and again at delivery time: require http(s) scheme, resolve the hostname, and reject any URL that resolves to a private/link-local/loopback/metadata IP range. Consider disabling redirects in the fetch call or re-validating the resolved IP after redirects.

Technical details

The vulnerability is a blind server-side request forgery (SSRF) in the alert channel webhook delivery mechanism. The webapp's DeliverAlertService fetches a user-supplied webhook URL without validating it against a blocklist of private/loopback/metadata IP ranges. An authenticated attacker can create a webhook alert channel with a URL pointing to internal infrastructure (e.g., 169.254.169.254) and trigger alert events (deployment failures, error groups) that cause the server to POST the signed alert payload to that internal URL. The attack requires prior authentication and API access but is blind (no response reflection) and POST-only; an attacker gains internal port/host discovery via timing oracles and can trigger state-changing requests to internal services.

Affected products

Trigger.dev Trigger.dev 5d99457 (HEAD/main)

Timeline

2026-10-02: disclosed

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