Quick answers
- Is CVE-2026-114073 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-114073 being exploited in the wild.
- How severe is CVE-2026-114073?
- Medium severity, with a CVSS score of 5.5, published 21 October 2026.
- Which products and versions are affected?
- Trigger.dev CLI before 4.5.9.
- Is there a fix for CVE-2026-114073?
- Yes: fixed in 4.5.9. Until then: Avoid running deployment commands with --log-level debug in production or shared environments. Review terminal transcripts, CI logs, and support bundles for exposed credentials and rotate any secrets that may have been captured. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-114073 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-114073?
- Check whether you run Trigger.dev CLI at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 4.5.9
Avoid running deployment commands with --log-level debug in production or shared environments. Review terminal transcripts, CI logs, and support bundles for exposed credentials and rotate any secrets that may have been captured.
Technical details
The vulnerability exists in the debug output serialization of the buildWorker options object, which logs the entire envVars property containing plaintext secret values. The issue affects versions prior to 4.5.9 and occurs when users run deploy commands with --log-level debug flag. Attack vector is local and requires user interaction (running the command); no authentication bypass or remote exploitation is possible, but recovered credentials enable access to databases and backend services.
Affected products
- Trigger.dev CLI before 4.5.9
Timeline
- 2026-07-31: disclosed
- 2026-10-21: advisory