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

CVE-2026-114076 · Severity: medium · CVSS 5.4 · Published 2026-10-21

Trigger.dev is a workflow automation platform that can send alert notifications via webhooks. An authenticated user can set an alert webhook URL pointing to internal services or cloud metadata endpoints, causing the server to make POST requests to those locations. An attacker could scan internal networks, modify internal services, or access cloud metadata to compromise the deployment.

Technologies: Trigger.dev. Vendors: Trigger.dev.

Quick answers

Is CVE-2026-114076 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-114076 being exploited in the wild.
How severe is CVE-2026-114076?
Medium severity, with a CVSS score of 5.4, published 21 October 2026.
Which products and versions are affected?
Trigger.dev before 4.5.2.
Is there a fix for CVE-2026-114076?
Yes: fixed in 4.5.2. Until then: Validate webhook URLs on creation and at fetch time to reject private IP ranges, loopback addresses, and metadata endpoints. Consider implementing egress filtering to block requests to private IP ranges and cloud metadata addresses at the network level. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-114076 attacked?
It is attacked over the network.
Am I affected by CVE-2026-114076?
Check whether you run 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.2

Validate webhook URLs on creation and at fetch time to reject private IP ranges, loopback addresses, and metadata endpoints. Consider implementing egress filtering to block requests to private IP ranges and cloud metadata addresses at the network level.

Technical details

A blind server-side request forgery exists in the alert channel webhook delivery mechanism. The webapp validates the webhook URL only as an optional string with no syntax or host checks, allowing authenticated tenants to point webhooks at private IP ranges, loopback addresses, or metadata services (169.254.169.254). When alerts fire, the alertsWorker delivers HMAC-signed POST payloads to the attacker-controlled URL via fetch(), which follows redirects and has no egress filtering, enabling internal port scanning, state-changing requests to internal services, and IMDSv1 access via redirect chains.

Affected products

  • Trigger.dev Trigger.dev before 4.5.2

Timeline

  • 2026-07-09: disclosed
  • 2026-10-21: advisory

References

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