ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-114073

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

Published Oct 2, 2026 · catalog updated Oct 21, 2026 · Trigger.dev: Trigger CLI debug

Open the advisory

Exploitation likelihood is not on this record for CVE-2026-114073. A missing EPSS score is not a low risk. Compare Trigger.dev: Trigger CLI debug with the linked advisory before you change production.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Trigger.dev: Trigger CLI debug).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
  • EPSS is missing. A missing score is not a low risk.
Severity
Medium5.5
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
Awaiting synchronization with FIRST
Remediation
Advisory link
Affected products
npm trigger.dev

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 . The debug output logged the complete build-worker options object. Its 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 debug record. 4. contains the plaintext value. No real credential is included in this report. The observed customer credentials are being rotated separately. Suggested remediation: never serialize 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.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • npm trigger.dev0 → 4.5.9

How to fix CVE-2026-114073

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

Exploitation likelihood is not on this record for CVE-2026-114073. A missing EPSS score is not a low risk. Compare Trigger.dev: Trigger CLI debug with the linked advisory before you change production.

Which versions are affected?

Compare what you have installed with 0 → 4.5.9. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-532: Insertion of Sensitive Information into Log File. EPSS is not on this record yet. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 2, 2026 · GitHub Advisory Database

    Detected

    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 . The debug output logged the complete build-worker options object. Its 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 ca

  2. Oct 21, 2026 · GitHub Advisory Database

    Fix available

    trigger.dev fixed in 4.5.9

  3. Oct 21, 2026 · GitHub Advisory Database

    Fix available

    trigger.dev fixed in 4.5.9

  4. Oct 21, 2026 · GitHub Advisory Database

    Updated

    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 . The debug output logged the complete build-worker options object. Its 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 ca

Sources

References

Freshness

Last verified in this catalog Oct 21, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.