Trigger.dev: Trigger CLI debug deployment logs expose resolved environment secret values — GHSA-FJ2X-MQQP-3V2W

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…

Timeline

Published by source

2026-10-02

Risk context

• Reported severity or threat level: medium.
• Reported CVSS score: 5.5 out of 10.
• Review exposure for the affected product or family: npm: trigger.dev.

Product

npm: trigger.dev

What to do

General, cautious steps (verify details in the official source):

• Review exposure and plan remediation based on risk and environment.
• Identify affected product versions in your inventory and verify whether you are impacted.
• Apply vendor patches/updates or recommended mitigations as soon as available.
• Read the official advisory for exact affected versions and remediation steps.

Official advisory

• Read the official source

Evidence and provenance

Canonical advisory ID

GHSA-FJ2X-MQQP-3V2W

Source

GitHub

Vendor

GitHub

Published by source

2026-10-02

Last source activity

2026-10-02

Curated by

hlukh.ch

Related advisories and connections

These advisories are connected by shared CVE, product, vendor, source, or time signals.