Medium 5.0Published Oct 20, 2026

CVE-2026-114080Trigger.dev before 4.5.2 Blind SSRF via Alert-Channel Webhook URL

Updated under an hour ago (Oct 28, 2026, 7:00 AM ET)

Does this affect you?

It affects triggerdotdev trigger.dev. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

Do this next

Start free and add your stack

Free account, 1 product

Every CVE for triggerdotdev trigger.dev

Exploited in the last 30 days

Trigger.dev before 4.5.2 contains a blind server-side request forgery vulnerability that allows authenticated project members to make the server send requests by setting unvalidated alert-channel webhook URLs. Attackers can create alert channels pointing to loopback, internal, or cloud metadata addresses, then trigger alerts to probe internal service reachability and send signed POST requests.

CVSS: 5.0 MEDIUM (v3.1, CNA)CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N
Weakness (CWE): CWE-918
Known exploited: Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days): Not loaded for this CVE
Assigned by: VulnCheck
NVD analysis: Deferred
Record last updated: Oct 21, 2026
First seen by InfoSec Signals: Oct 20, 2026

Affected products

Affected products

triggerdotdev trigger.dev triggerdotdev:trigger.dev (from the name)	before 4.5.2; 4.5.2 not affected	CNA record

References

References

https://github.com/triggerdotdev/trigger.dev/security/advisories/GHSA-2wgf-7gx2-hcpw	vendor-advisory
https://www.vulncheck.com/advisories/trigger-dev-before-4.5.2-blind-ssrf-via-alert-channel-webhook-url-2	third-party-advisory

The CVE record on cve.org NVD's entry

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.