Skip to main content
VulnerabilityPublished

Trigger.dev: Blind SSRF via alert-channel webhook

Affects trigger.devSource GCVE Database

0

CVSS 5.4 Medium : upgrade to 4.5.2 when convenient.

Data as of 3 Oct 2026, 17:41 UTC

CVSS 3.1 base score
5.4Medium
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 4.5.2
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

What to do

Upgrade trigger.dev to 4.5.2.

Affected software

ProductAffectedFixed in
npmtrigger.devAffected
  • <4.5.2
Fixed in
  • 4.5.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available for this vulnerability. The recommended remediation is to validate webhook URLs upon creation by enforcing HTTP(S) schemes and rejecting private, link-local, loopback, and metadata IP ranges. Additionally, the URL should be re-validated at fetch time, including after redirects, or redirects should be disabled/pinned to resolved public IPs. Implementing a shared assertion function (e.g., assertPublicUrl) for URL validation in both creation and delivery code paths is advised.

Description

Trigger.dev contains a blind Server-Side Request Forgery (SSRF) vulnerability in its webhook alert channel implementation. Authenticated tenants can configure webhook URLs without validation, allowing the server to POST alert payloads to internal or metadata service IP addresses. This can lead to internal host scanning, state-changing POST requests to internal services, and potential access to IMDSv1 via redirects. The vulnerability affects versions prior to 4.5.2. A fix is available that includes validating webhook URLs against private, link-local, loopback, and metadata IP ranges and re-checking URLs at fetch time.

References

Community reviews

Loading reviews…