Vulnerability Database · npm · trigger.dev · Version
trigger.dev 4.5.6
4.5.6 is affected by 1 vulnerability.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to.
Critical 0 High 0 Medium 1 Low 0 Unrated 0
-
Released 21 Jul 2026
Licence MIT
Also known from other sources 1
Newer releases 300
Database updated 22/Oct/2026
Release and licence data published by the npm registry. Licence information is not legal advice.
Concerned about your application's security?
Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.
01 Vulnerabilities affecting this version
trigger.dev 4.5.6 vulnerabilities
1 vulnerability cover trigger.dev 4.5.6. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| Exposed Secrets in Debug Logs of Trigger.dev Package | 5.5 medium | 4.5.9 | 02 Oct 2026 |
Looking for another version, or everything Vulert holds for trigger.dev?
Questions
About trigger.dev 4.5.6
Is trigger.dev 4.5.6 vulnerable?
Yes. 1 vulnerability in the Vulert database cover trigger.dev 4.5.6: 0 critical, 0 high, 1 medium and 0 low. Each entry above names the fixed version to move to.
Is 4.5.6 the latest release of trigger.dev?
No. 4.5.6 was published 21 Jul 2026, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.
How do I monitor trigger.dev for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the trigger.dev version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.