Vulnerability Database · npm · trigger.dev · Version

trigger.dev 4.5.0-rc.3

4.5.0-rc.3 is affected by 10 vulnerabilities.

The vulnerabilities that cover this exact version are listed below with the fixed version to move to.

Critical 1 High 5 Medium 4 Low 0 Unrated 0

Released 01 Jun 2026 Licence MIT Also known from other sources 10 Newer releases 300 Database updated 23/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.

Looking for another version, or everything Vulert holds for trigger.dev?

All versions → Full vulnerability list →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About trigger.dev 4.5.0-rc.3

Is trigger.dev 4.5.0-rc.3 vulnerable?

Yes. 10 vulnerabilities in the Vulert database cover trigger.dev 4.5.0-rc.3: 1 critical, 5 high, 4 medium and 0 low. Each entry above names the fixed version to move to.

Is 4.5.0-rc.3 the latest release of trigger.dev?

No. 4.5.0-rc.3 was published 01 Jun 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.