CVE-2026-114076: Trigger.dev before 4.5.2 Blind SSRF via Alert Channel Webhook URL
triggerdotdev · trigger.dev
Fixed in 4.5.2 · Affected: triggerdotdev trigger.dev before 4.5.2 · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 26% of scored CVEs
DescriptionCVE.org
Trigger.dev before 4.5.2 contains a blind server-side request forgery vulnerability that allows authenticated tenants to make the webapp server send POST requests to internal hosts by setting an unvalidated webhook alert channel URL. Attackers can point the webhook at internal services or cloud metadata addresses and trigger alerts to scan internal hosts, send state-changing POSTs, or reach IMDSv1 via redirects.
Affected products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- triggerdotdev · trigger.devbefore 4.5.2
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Weakness
- Server-Side Request Forgery
- Vendor
- triggerdotdev
- Published
- October 2026
CoverageNo articles yet
No CyberSIXT article names CVE-2026-114076 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.