Vulnerabilities in pkg:npm/trigger.dev

PACKAGE
Advisory Summary

GHSA-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.

10 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:npm/trigger.dev

10 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:npm/trigger.dev. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-fj2x-mqqp-3v2w - MODERATE Trigger.dev: Trigger CLI debug deployment logs expose resolved environment secret values
GHSA-4672-hwv6-gq62 - MODERATE Trigger.dev: Cross-environment deployment cancel
GHSA-9q4r-4842-93vw - HIGH Trigger.dev: Cross-tenant SQL injection in the TSQL query compiler (POST /api/v1/query) via unsanitized window-function name
GHSA-pqxw-g93w-hj9x - HIGH Trigger.dev Self-Hosted Deployment: Default Secrets allow Unauthenticated Infrastructure Compromise
GHSA-59h8-w5q6-mfmp - MODERATE Trigger.dev: Unauthenticated Realtime Stream Data Injection via Run FriendlyId
GHSA-gg6r-gp4c-89hp - CRITICAL Trigger.dev: V1 coordinator default-secret unauth Socket.IO
GHSA-q567-cr4x-96w4 - MODERATE Trigger.dev: Blind SSRF via alert-channel webhook
GHSA-pp95-gc86-jq6q - HIGH Trigger.dev: Missing Authentication in Run Replay Action Allows Cross-Organization Task Execution (IDOR)
GHSA-xxv7-2vv3-h682 - HIGH Trigger.dev: Server-side request forgery via unvalidated webhook alert-channel URL
GHSA-qxpp-qjg8-x4jv - HIGH Trigger.dev: Run replay injects a task run into an attacker-chosen environment (cross-tenant write)

GHSA-fj2x-mqqp-3v2w at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-fj2x-mqqp-3v2w
Severity MODERATE
CVSS v3.1 Base Score 5.5
CWE Classification CWE-532: Insertion of Sensitive Information into Log File
Affected Product Trigger.dev
Package Ecosystem npm
Published Date
Last Updated

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).

Attack Vector Local (AV:L)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction Required (UI:R)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity None (I:N)
Availability None (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.

trigger.dev fixed: 4.5.9
npm install trigger.dev@4.5.9
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls trigger.dev

How 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.dev

Analyze 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

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: 1. Configure a Trigger.dev project with a secret environment variable. 2. Run the command above with an authenticated profile. 3. Inspect the `Starting buildWorker` debug record. 4. `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.

GHSA-fj2x-mqqp-3v2w Affected Trigger.dev Versions

1 component(s)
Fixed Versions:
4.5.9
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?
GHSA-fj2x-mqqp-3v2w is a security vulnerability in Trigger.dev involving Trigger CLI debug deployment logs expose resolved environment secret values under CWE-532: Insertion of Sensitive Information into Log File.
Which Trigger.dev versions are affected?
Affected versions include releases prior to 4.5.9 across affected packages: trigger.dev.
What version fixes GHSA-fj2x-mqqp-3v2w?
Upgrading to 4.5.9 (or the latest patched release for your respective branch) resolves the vulnerability.
Is trigger.dev affected?
Yes, trigger.dev is affected in releases prior to 4.5.9. Upgrade your dependency to 4.5.9 or later.
What is the CVSS score of GHSA-fj2x-mqqp-3v2w?
GHSA-fj2x-mqqp-3v2w has a CVSS v3.1 base score of 5.5 (MODERATE) with vector string CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N.
What CWE is associated with GHSA-fj2x-mqqp-3v2w?
GHSA-fj2x-mqqp-3v2w is classified under CWE-532: Insertion of Sensitive Information into Log File (The product writes sensitive information to a log file.).
How can I check npm dependencies for GHSA-fj2x-mqqp-3v2w?
Run the dependency tree command: 'npm ls trigger.dev'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "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
  }
}