Advisory record · GHSA-pqxw-g93w-hj9x

Trigger.dev Self-Hosted Deployment: Default Secrets allow Unauthenticated Infrastructure Compromise

CVSS 9.2 CriticalCriticalEPSS 0.0051 · 43rd percentile

Critical, because:

  • CVSS score 9.2: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 2 Oct 2026, 22:39 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
trigger.devnpm<4.5.64.5.6
Identifiers
GHSA-pqxw-g93w-hj9x · CVE-2026-114087
Weakness (CWE)
CWE-653 · CWE-1393
Published
2 Oct 2026
Updated
21 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Trigger.dev self-hosted v4 deployments before 4.5.6 (npm package trigger.dev) that use the default secrets in the provided Docker Compose example configuration are affected. An unauthenticated attacker who knows those published default secrets can forge login links for any email address, then reach internal services such as the database, Redis and ClickHouse, which the source says lack proper authentication. The source describes complete compromise of tenant data and infrastructure. Upgrade to version 4.5.6 or later, and replace the default secrets in the example environment file.

Written 31 Oct 2026.

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

ScoreRatingCVSSVectorSource
9.2 Critical 4.0 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N CNA (VulnCheck)
  • CISA KEV Not listed.
  • EPSS 0.0051, the 43rd percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 13:33 UTC First seen by agentprime
  2. 31 Oct 2026, 13:33 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.