Trigger.dev: Trigger CLI debug deployment logs expose resolved environment secret values
Affects trigger.devSource GCVE Database
CVSS 5.5 Medium : upgrade to 4.5.9 when convenient.
Data as of 3 Oct 2026, 17:39 UTC
- Patch
- Available – fixed in 4.5.9
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:NWhat to do
Upgrade trigger.dev to 4.5.9.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npmtrigger.dev | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch is available that prevents serialization of secret environment variable values in debug output. Users should upgrade to version 4.5.9 or later where this issue is fixed. Until patched, avoid running deployments with debug logging enabled in environments containing sensitive secrets. The vendor recommends logging only environment variable names or replacing secret values with fixed markers in debug logs. Additionally, regression tests should be added to prevent recurrence.
Description
Trigger.dev version 4.5.3 and earlier versions prior to 4.5.9 have a vulnerability where debug deployment logs expose resolved environment secret values in plaintext. When running a dry-run deployment with debug logging enabled, the complete environment variables including secrets such as database connection strings and service credentials are logged unredacted. This exposure occurs even though no actual deployment takes place. The issue allows anyone with access to debug logs or terminal transcripts to recover sensitive deployment secrets.
References
- github.com/triggerdotdev/trigger.dev/security/advisories/GHSA-fj2x-mqqp-3v2w (opens in a new tab)
- github.com/triggerdotdev/trigger.dev/pull/4420 (opens in a new tab)
- github.com/triggerdotdev/trigger.dev/commit/878c15811aca8339a751aa0c2211012db7a47ce5 (opens in a new tab)
- github.com/triggerdotdev/trigger.dev (opens in a new tab)
- github.com/triggerdotdev/trigger.dev/releases/tag/v4.5.9 (opens in a new tab)