trigger.dev
Affected
- introduced
0, fixed4.5.9(semver)
Fixed versions
4.5.9
Fix
- Fixed version
4.5.9npm install [email protected]
Advisory
Also known as: CVE-2026-114073
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. 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:
Starting buildWorker debug record.options.envVars contains 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.
Medium Basis: The source's own band: MODERATE
0, fixed 4.5.9 (semver)4.5.9
4.5.9npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0