Skip to content
Heist/ feed
Back to feed
MediumFix available

Trigger.dev: Trigger CLI debug deployment logs expose resolved environment secret values

Type: advisorySources: OSV

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.

Products
trigger.dev
Affected versions
Not specified
Fixed versions
4.5.9
CVEs
CVE-2026-114073
Confirmed fixed CVEs
Not specified
Updated in this feed
31 Oct 2026, 14:09 UTC · Revision 1

Source evidence

Trigger.dev: Trigger CLI debug deployment logs expose resolved environment secret values

core-osv · Original source

Published 2 Oct 2026, 22:45 UTC

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.

osv:GHSA-fj2x-mqqp-3v2w

trigger.dev

Fixed versions: 4.5.9

Complete source record
{
  "id": "1779ec1d5d387098e74660f8d6681c27855f1c2ff3c41c2d7463b43c6e2114f8",
  "url": "https://osv.dev/vulnerability/GHSA-fj2x-mqqp-3v2w",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "Trigger.dev: Trigger CLI debug deployment logs expose resolved environment secret values",
    "summary": "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.",
    "evidence": "osv:GHSA-fj2x-mqqp-3v2w",
    "products": [
      {
        "name": {
          "value": "trigger.dev",
          "evidence": "/affected/0/package/name"
        },
        "prerequisites": [],
        "fixed_versions": [
          {
            "value": "4.5.9",
            "evidence": "/affected/0/ranges"
          }
        ],
        "affected_versions": []
      }
    ],
    "severity": "medium",
    "structured": {
      "id": "GHSA-fj2x-mqqp-3v2w",
      "aliases": [
        "CVE-2026-114073",
        "GHSA-fj2x-mqqp-3v2w"
      ],
      "metrics": [
        {
          "type": "CVSS_V3",
          "score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N"
        }
      ],
      "affected": [
        {
          "ranges": [
            {
              "type": "SEMVER",
              "events": [
                {
                  "introduced": "0"
                },
                {
                  "fixed": "4.5.9"
                }
              ]
            }
          ],
          "package": {
            "name": "trigger.dev",
            "purl": "pkg:npm/trigger.dev",
            "ecosystem": "npm"
          },
          "database_specific": {
            "source": "https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/10/GHSA-fj2x-mqqp-3v2w/GHSA-fj2x-mqqp-3v2w.json",
            "last_known_affected_version_range": "<= 4.5.8"
          }
        }
      ],
      "modified": "2026-10-21T10:57:26.665490472Z",
      "provider": "osv",
      "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",
        "https://github.com/triggerdotdev/trigger.dev/releases/tag/v4.5.9"
      ],
      "provider_metadata": {
        "cwe_ids": [
          "CWE-532"
        ],
        "severity": "MODERATE",
        "github_reviewed": true,
        "nvd_published_at": null,
        "github_reviewed_at": "2026-10-02T22:45:12Z"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2026-114073",
        "evidence": "/aliases"
      }
    ],
    "security_relevant": true,
    "severity_evidence": "/severity/0/score"
  },
  "source_id": "core-osv",
  "document_id": 392983,
  "published_at": "2026-10-02T22:45:12+00:00"
}