Trigger.dev: Server-side request forgery via unvalidated webhook alert-channel URL — GHSA-XXV7-2VV3-H682

Summary

### Summary A project member can create a webhook alert channel whose delivery URL points at an internal address, and trigger.dev's control plane will send the alert there with no SSRF protection. The webhook URL is stored as an unvalidated string and is fetched directly from the webapp server, so a low-privilege authenticated user can make the server issue POST requests to internal-only services and cloud metadata…

Timeline

Published by source

2026-10-02

Risk context

• Reported severity or threat level: high.
• Reported CVSS score: 7.7 out of 10.
• Review exposure for the affected product or family: npm: trigger.dev.

Product

npm: trigger.dev

What to do

General, cautious steps (verify details in the official source):

• Prioritize patching or mitigation immediately (treat as actively risky).
• Identify affected product versions in your inventory and verify whether you are impacted.
• Apply vendor patches/updates or recommended mitigations as soon as available.
• Read the official advisory for exact affected versions and remediation steps.

Official advisory

• Read the official source

Evidence and provenance

Canonical advisory ID

GHSA-XXV7-2VV3-H682

Source

GitHub

Vendor

GitHub

Published by source

2026-10-02

Last source activity

2026-10-02

Curated by

hlukh.ch

Related advisories and connections

These advisories are connected by shared CVE, product, vendor, source, or time signals.