GHSA-fj2x-mqqp-3v2w: Trigger.dev Trigger CLI Debug Deployment Logs Vulnerability
MODERATEGHSA-fj2x-mqqp-3v2w is a MODERATE (CVSS 5.5) trigger cli debug deployment logs vulnerability (CWE-532: Insertion of Sensitive Information into Log File) affecting Trigger.dev libraries in the npm ecosystem. The issue involves trigger cli debug deployment logs expose resolved environment secret values. Remediation is available by upgrading affected packages to version 4.5.9.
GHSA-fj2x-mqqp-3v2w at a Glance
Security Impact
CVSS: 5.5
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N).
How to Fix GHSA-fj2x-mqqp-3v2w
To remediate this vulnerability, upgrade all affected Trigger.dev dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
npm install trigger.dev@4.5.9Run the following command in your project directory to verify that all resolved dependencies use the patched release:
npm ls trigger.devHow to Check if You Are Affected
To determine whether your Node.js application is affected by GHSA-fj2x-mqqp-3v2w, inspect your project dependencies using npm:
npm ls trigger.devAnalyze the terminal output to locate any version of Trigger.dev in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 4.5.9), your application is affected.
Note: The npm ls trigger.dev command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-532: Insertion of Sensitive Information into Log File, where the product writes sensitive information to a log file. In Trigger.dev, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
GHSA-fj2x-mqqp-3v2w Affected Trigger.dev Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
trigger.dev
|
npm |
< 4.5.9
|
4.5.9
|
References
Frequently Asked Questions
What is GHSA-fj2x-mqqp-3v2w?
Which Trigger.dev versions are affected?
What version fixes GHSA-fj2x-mqqp-3v2w?
Is trigger.dev affected?
What is the CVSS score of GHSA-fj2x-mqqp-3v2w?
What CWE is associated with GHSA-fj2x-mqqp-3v2w?
How can I check npm dependencies for GHSA-fj2x-mqqp-3v2w?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-fj2x-mqqp-3v2w",
"modified" : "2026-10-02T22:45:12Z",
"published" : "2026-10-02T22:45:12Z",
"aliases" : [ ],
"summary" : "Trigger.dev: Trigger CLI debug deployment logs expose resolved environment secret values",
"details" : "Affected version: trigger.dev 4.5.3 (4.5.6 was advertised by the CLI but was not tested).\n\nA 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.\n\nImpact: 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.\n\nReproduction:\n1. Configure a Trigger.dev project with a secret environment variable.\n2. Run the command above with an authenticated profile.\n3. Inspect the `Starting buildWorker` debug record.\n4. `options.envVars` contains the plaintext value.\n\nNo real credential is included in this report. The observed customer credentials are being rotated separately.\n\nSuggested 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.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "npm",
"name" : "trigger.dev"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "4.5.9"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 4.5.8"
}
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/triggerdotdev/trigger.dev/security/advisories/GHSA-fj2x-mqqp-3v2w"
}, {
"type" : "WEB",
"url" : "https://github.com/triggerdotdev/trigger.dev/pull/4420"
}, {
"type" : "WEB",
"url" : "https://github.com/triggerdotdev/trigger.dev/commit/878c15811aca8339a751aa0c2211012db7a47ce5"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/triggerdotdev/trigger.dev"
}, {
"type" : "WEB",
"url" : "https://github.com/triggerdotdev/trigger.dev/releases/tag/v4.5.9"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-532" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2026-10-02T22:45:12Z",
"nvd_published_at" : null
}
}