Is CVE-2026-85650 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-85650 being exploited in the wild.

How severe is CVE-2026-85650?

Medium severity, with a CVSS score of 5.4, published 4 September 2026.

Which products and versions are affected?

trigger.dev (npm) SEMVER:introduced=0,fixed=4.5.2; Trigger.dev before 4.5.2.

Is there a fix for CVE-2026-85650?

Yes. trigger.dev (npm): upgrade to 4.5.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-85650 attacked?

It is attacked over the network.

Am I affected by CVE-2026-85650?

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.

CVE-2026-85650: Trigger.dev server-side request forgery in webhook alert delivery

CVE-2026-85650 · Severity: medium · CVSS 5.4 · Published 2026-09-04

Trigger.dev is a platform for building and deploying AI agents and workflows. A server-side request forgery (SSRF) vulnerability in the alert channel feature allows authenticated organization members to create webhook URLs that target internal services and metadata endpoints, enabling the server to make unauthorized POST requests to restricted resources on the internal network.

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

Quick answers

Is CVE-2026-85650 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-85650 being exploited in the wild.
How severe is CVE-2026-85650?: Medium severity, with a CVSS score of 5.4, published 4 September 2026.
Which products and versions are affected?: trigger.dev (npm) SEMVER:introduced=0,fixed=4.5.2; Trigger.dev before 4.5.2.
Is there a fix for CVE-2026-85650?: Yes. trigger.dev (npm): upgrade to 4.5.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-85650 attacked?: It is attacked over the network.
Am I affected by CVE-2026-85650?: 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

trigger.dev (npm): upgrade to 4.5.2 or later
```
npm install trigger.dev@4.5.2
```

Technical details

Trigger.dev before version 4.5.2 contains an SSRF vulnerability in the webhook alert channel delivery URL handling. The vulnerability exists because webhook URLs are fetched and POST requests are issued without proper URL validation or SSRF protection mechanisms. Authenticated users with organization membership can exploit this by configuring alert channels with URLs pointing to internal services (e.g., metadata endpoints, internal APIs). This allows an attacker to leverage the server to send requests to restricted internal resources that would normally be unreachable from the external network. The fix was released in version 4.5.2.

Affected products

Trigger.dev Trigger.dev before 4.5.2

Identifiers

CVE-2026-85650
GHSA-xxv7-2vv3-h682

Timeline

2026-09-04: disclosed
2026-07-09: patched: Version 4.5.2 released with security fix

References

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