Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Trigger.dev versions before 4.5.2 are affected by a server-side request forgery issue in the alert-channel webhook feature. An authenticated user can set a webhook URL that the webapp server then sends alert POSTs to, without any check against internal or private addresses. The attacker can therefore make the server send requests to internal hosts, which the source describes as enabling port scanning and state-changing POSTs to internal services; the response is not returned to the attacker. Upgrade to trigger.dev 4.5.2, which is the fixed version listed.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 5.3 | Medium | 4.0 | CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N | CNA (VulnCheck) |
- CISA KEV Not listed.
- EPSS 0.0033, the 26th percentile, on 7 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 13:33 UTC First seen by agentprime
- 31 Oct 2026, 13:33 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-q567-cr4x-96w4
- OSV: GHSA-q567-cr4x-96w4
- github.com/triggerdotdev/trigger.dev/security/advisories/GHSA-q567-cr4x-96w4
- github.com/triggerdotdev/trigger.dev/pull/4199
- github.com/triggerdotdev/trigger.dev/commit/34b1a181c2a1d33a53ebab88f84b05f81fea4254
- github.com/triggerdotdev/trigger.dev
- github.com/triggerdotdev/trigger.dev/releases/tag/v4.5.2