Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.4amended

Trigger.dev: Blind SSRF via alert-channel webhook

CVE-2026-114076GHSA-q567-cr4x-96w4

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (trigger.dev 4.5.2), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
5.4 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
EPSS
  • CVE-2026-114076: 0.33% estimated exploitation activity in the next 30 days; percentile 26.17 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary A WEBHOOK alert channel stores a user-supplied url. When an alert fires (deployment/run failure, error groups), the webapp server (alertsWorker - DeliverAlertService) POSTs the HMAC-signed alert payload to that URL via fetch(webhook.url, ...). The URL is never validated against a host allowlist or private-IP/metadata blocklist (a repo-wide search for 169.254, isPrivate, isLoopback, net.isIP, ssrf returns ZERO hits), and the API route's URL field is just z.string().optional() (no syntax check at all). So an authenticated tenant can point the webhook at internal infrastructure or 169.254.169.254 and the multi-tenant server fetches it. Affected apps/webapp, HEAD 5d99457 (current main). Root cause - Source (API route): app/presenters/v3/ApiAlertChannelPresenter.server.ts ApiAlertChannelData.url = z.string().optional() (no host validation); route app/routes/api.v1.projects.$projectRef.alertChannels.ts (PAT-auth). - Store: app/v3/services/alerts/createAlertChannel.server.ts…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-q567-cr4x-96w4

  2. Revision 2 · amended ·

    Amended from osv record GHSA-q567-cr4x-96w4

  3. Revision 1 · created ·

    Published from ghsa record GHSA-q567-cr4x-96w4

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-114076

Advisory: Trigger.dev: Blind SSRF via alert-channel webhook
IDs: CVE-2026-114076, GHSA-q567-cr4x-96w4
Record: https://patchnext.com/advisories/ghsa-q567-cr4x-96w4 (revision 3, source checked 26 Oct 2026, 13:06 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: trigger.dev 4.5.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm trigger.dev: affected <= 4.5.1; fixed in 4.5.2

## Suggested inspection (read-only)
- `npm ls trigger.dev --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on trigger.dev.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-q567-cr4x-96w4 (GitHub-reviewed advisory GHSA-q567-cr4x-96w4 lists affected ranges: npm trigger.dev >=0 <=4.5.1)
- Verified: https://osv.dev/vulnerability/GHSA-q567-cr4x-96w4 (OSV record GHSA-q567-cr4x-96w4 lists affected ranges: npm trigger.dev >=0 <4.5.2 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…