GHSA-fj2x-mqqp-3v2w: Trigger.dev: Trigger CLI debug deployment logs expose resolved environment secret values
Affected version: trigger.dev 4.5.3 (4.5.6 was advertised by the CLI but was not tested). A staging dry-run executed with trigger.dev deploy --env staging --dry-run --log-level debug. The debug output logged the complete build-worker options object. Its envVars property contained unredacted values for every resolved staging variable, including database connection strings and service credentials.
Published Oct 2, 2026
Affected packages
trigger.dev
- Ecosystem
- npm
- Affected
- <= 4.5.8
- Fixed in
- 4.5.9
- Check
npm ls trigger.dev
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Affected version: trigger.dev 4.5.3 (4.5.6 was advertised by the CLI but was not tested).
A staging dry-run executed with trigger.dev deploy --env staging --dry-run --log-level debug. The debug output logged the complete build-worker options object. Its envVars property contained unredacted values for every resolved staging variable, including database connection strings and service credentials. The non-debug environment listing correctly hides values, so users can reasonably expect deployment logs not to print secrets.
Impact: anyone with access to a developer terminal transcript, CI debug log, captured agent/tool output, or support bundle can recover deployment secrets even though no deployment occurs.
Reproduction:
- Configure a Trigger.dev project with a secret environment variable.
- Run the command above with an authenticated profile.
- Inspect the
Starting buildWorkerdebug record. options.envVarscontains the plaintext value.
No real credential is included in this report. The observed customer credentials are being rotated separately.
Suggested remediation: never serialize envVars values in debug output; log names only or replace every value with a fixed marker. Add regression coverage for deploy, dry-run, and debug logging, and review adjacent debug records for resolved secrets.
References
- https://github.com/triggerdotdev/trigger.dev/security/advisories/GHSA-fj2x-mqqp-3v2w
- https://github.com/triggerdotdev/trigger.dev/pull/4420
- https://github.com/triggerdotdev/trigger.dev/commit/878c15811aca8339a751aa0c2211012db7a47ce5
- https://github.com/triggerdotdev/trigger.dev/releases/tag/v4.5.9
- https://github.com/advisories/GHSA-fj2x-mqqp-3v2w
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesGHSA-4672-hwv6-gq62
Trigger.dev: Cross-environment deployment cancel
medium5.4Oct 2, 2026GHSA-59h8-w5q6-mfmp
Trigger.dev: Unauthenticated Realtime Stream Data Injection via Run FriendlyId
medium5.3Oct 2, 2026GHSA-9q4r-4842-93vw
Trigger.dev: Cross-tenant SQL injection in the TSQL query compiler (POST /api/v1/query) via unsanitized window-function name
high7.7Oct 2, 2026GHSA-gg6r-gp4c-89hp
Trigger.dev: V1 coordinator default-secret unauth Socket.IO
critical9.2Oct 2, 2026GHSA-pp95-gc86-jq6q
Trigger.dev: Missing Authentication in Run Replay Action Allows Cross-Organization Task Execution (IDOR)
high7.1Oct 2, 2026GHSA-pqxw-g93w-hj9x
Trigger.dev Self-Hosted Deployment: Default Secrets allow Unauthenticated Infrastructure Compromise
high8.1Oct 2, 2026
