VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

trigger.dev: vulnerability history, versions and safety

trigger.dev is a package in the npm ecosystem. Vulert records 10 vulnerabilities for it across 97 releases, first recorded in Oct 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
10 vulnerabilities recorded C1 H5 M4
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
10 in the last 12 months

Most recent disclosure 02 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all trigger.dev vulnerabilities

Vulert verdict on trigger.dev 4.7.7 i

Updated on 22 Oct 2026

Good news: 4.7.7, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 10.

Package health score 69/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Active

What to do: Stay on 4.7.7 or newer. This can change: a vulnerability disclosed tomorrow can affect 4.7.7 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 4.7.7 — unaffected i
  • Vulnerabilities on record 10 over 1 year · 10 in the last year i
  • Latest disclosure 02 Oct 2026 i
  • Highest CVSS 9.2 i
  • With no published fix 0 i
  • Stars 16,551 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 22 Oct 2026. 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 Versions

Which versions are affected

Every version Vulert tracks for trigger.dev, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
4.7.7 22 Oct 2026 none MIT — Details →
0.0.0-rc-4-8-0-20261021151928 21 Oct 2026 C1 H5 M4 MIT Yes Details →
4.7.6 20 Oct 2026 none MIT — Details →
4.7.5 20 Oct 2026 none MIT — Details →
4.8.0-webhooks.20261020092920 20 Oct 2026 none MIT — Details →
4.8.0-webhooks.20261015065339 15 Oct 2026 none MIT — Details →
4.7.4 14 Oct 2026 none MIT — Details →
0.0.0-prerelease-redis-worker-fix-20261013-20261013141038 13 Oct 2026 C1 H5 M4 MIT Yes Details →
4.7.3 06 Oct 2026 none MIT — Details →
4.7.2 02 Oct 2026 none MIT — Details →
4.7.1 02 Oct 2026 none MIT — Details →
4.7.0 01 Oct 2026 none MIT — Details →
0.0.0-prerelease-windows-bundle-fix-20260928100448 28 Sep 2026 C1 H5 M4 MIT Yes Details →
4.6.4 22 Sep 2026 none MIT — Details →
4.6.3 17 Sep 2026 none MIT — Details →
4.6.2 16 Sep 2026 none MIT — Details →
4.6.1 15 Sep 2026 none MIT — Details →
4.6.0 14 Sep 2026 none MIT — Details →
0.0.0-prerelease-20260911153544 11 Sep 2026 C1 H5 M4 MIT Yes Details →
0.0.0-prerelease-20260911094758 11 Sep 2026 C1 H5 M4 MIT Yes Details →
0.0.0-bun-prerelease-20260909132648 09 Sep 2026 C1 H5 M4 MIT Yes Details →
0.0.0-bun-runtimes-20260909131057 09 Sep 2026 C1 H5 M4 MIT Yes Details →
0.0.0-prerelease-20260909121655 09 Sep 2026 C1 H5 M4 MIT Yes Details →
0.0.0-prerelease-streamfix-20260909094302 09 Sep 2026 C1 H5 M4 MIT Yes Details →
0.0.0-prerelease-20260909071038 09 Sep 2026 C1 H5 M4 MIT Yes Details →
0.0.0-prerelease-20260908122921 08 Sep 2026 C1 H5 M4 MIT Yes Details →
4.5.16 02 Sep 2026 none MIT — Details →
0.0.0-prerelease-nodemodule-exclude-fix-20260902142214 02 Sep 2026 C1 H5 M4 MIT Yes Details →
0.0.0-prerelease-nodemodule-copy-fix-20260902124940 02 Sep 2026 C1 H5 M4 MIT Yes Details →
4.5.15 31 Aug 2026 none MIT — Details →
4.5.14 28 Aug 2026 none MIT — Details →
0.0.0-prerelease-20260828141059 28 Aug 2026 C1 H5 M4 MIT Yes Details →
4.5.13 28 Aug 2026 none MIT — Details →
0.0.0-prerelease-server-set-build-path-20260828082517 28 Aug 2026 C1 H5 M4 MIT Yes Details →
0.0.0-prerelease-20260827143549 27 Aug 2026 C1 H5 M4 MIT Yes Details →
0.0.0-prerelease-20260827125919 27 Aug 2026 C1 H5 M4 MIT Yes Details →
0.0.0-prerelease-local-bundle-20260825080823 25 Aug 2026 C1 H5 M4 MIT Yes Details →
0.0.0-prerelease-local-bundle-20260824142657 24 Aug 2026 C1 H5 M4 MIT Yes Details →
4.5.12 20 Aug 2026 none MIT — Details →
0.0.0-prerelease-deployment-base-image-20260814120901 14 Aug 2026 C1 H5 M4 MIT Yes Details →
4.5.11 13 Aug 2026 none MIT — Details →
0.0.0-prerelease-20260810145618 10 Aug 2026 C1 H5 M4 MIT Yes Details →
4.5.10 07 Aug 2026 none MIT — Details →
0.0.0-v4-prerelease-20260807113753 07 Aug 2026 C1 H5 M4 MIT Yes Details →
4.5.9 30 Jul 2026 none MIT — Details →
4.5.8 27 Jul 2026 M1 MIT Yes Details →
4.5.7 23 Jul 2026 M1 MIT Yes Details →
4.5.6 21 Jul 2026 M1 MIT Yes Details →
4.5.5 20 Jul 2026 H2 M2 MIT Yes Details →
4.5.4 14 Jul 2026 H2 M3 MIT Yes Details →
4.5.3 10 Jul 2026 C1 H2 M3 MIT Yes Details →
4.5.2 09 Jul 2026 C1 H2 M3 MIT Yes Details →
4.5.1 06 Jul 2026 C1 H5 M4 MIT Yes Details →
4.5.0 02 Jul 2026 C1 H5 M4 MIT Yes Details →
4.5.0-rc.7 17 Jun 2026 C1 H5 M4 MIT Yes Details →
4.5.0-rc.6 12 Jun 2026 C1 H5 M4 MIT Yes Details →
4.5.0-rc.5 05 Jun 2026 C1 H5 M4 MIT Yes Details →
4.5.0-rc.4 02 Jun 2026 C1 H5 M4 MIT Yes Details →
4.5.0-rc.3 01 Jun 2026 C1 H5 M4 MIT Yes Details →
4.5.0-rc.2 23 May 2026 C1 H5 M4 MIT Yes Details →
4.5.0-rc.1 21 May 2026 C1 H5 M4 MIT Yes Details →
0.0.0-chat-prerelease-20260521151946 21 May 2026 C1 H5 M4 MIT Yes Details →
4.5.0-rc.0 21 May 2026 C1 H5 M4 MIT Yes Details →
0.0.0-chat-prerelease-20260520150857 20 May 2026 C1 H5 M4 MIT Yes Details →
0.0.0-chat-prerelease-20260519091352 19 May 2026 C1 H5 M4 MIT Yes Details →
0.0.0-chat-prerelease-20260517214402 17 May 2026 C1 H5 M4 MIT Yes Details →
4.4.6 12 May 2026 C1 H5 M4 MIT Yes Details →
0.0.0-prerelease-20260508094307 08 May 2026 C1 H5 M4 MIT Yes Details →
0.0.0-prerelease-20260508090504 08 May 2026 C1 H5 M4 MIT Yes Details →
0.0.0-chat-prerelease-20260507131256 07 May 2026 C1 H5 M4 MIT Yes Details →
0.0.0-chat-prerelease-20260507122230 07 May 2026 C1 H5 M4 MIT Yes Details →
0.0.0-prerelease-20260506144322 06 May 2026 C1 H5 M4 MIT Yes Details →
0.0.0-prerelease-20260506134321 06 May 2026 C1 H5 M4 MIT Yes Details →
0.0.0-prerelease-20260506133747 06 May 2026 C1 H5 M4 MIT Yes Details →
0.0.0-chat-prerelease-20260506093419 06 May 2026 C1 H5 M4 MIT Yes Details →
0.0.0-chat-prerelease-20260505140031 05 May 2026 C1 H5 M4 MIT Yes Details →
0.0.0-chat-prerelease-20260505084711 05 May 2026 C1 H5 M4 MIT Yes Details →
0.0.0-chat-prerelease-20260502065709 02 May 2026 C1 H5 M4 MIT Yes Details →
4.4.5 01 May 2026 C1 H5 M4 MIT Yes Details →
0.0.0-chat-prerelease-20260501122331 01 May 2026 C1 H5 M4 MIT Yes Details →
0.0.0-prerelease-20260428085845 28 Apr 2026 C1 H5 M4 MIT Yes Details →
0.0.0-chat-prerelease-20260419173457 19 Apr 2026 C1 H5 M4 MIT Yes Details →
0.0.0-chat-prerelease-20260418174118 18 Apr 2026 C1 H5 M4 MIT Yes Details →
0.0.0-chat-prerelease-20260418083610 18 Apr 2026 C1 H5 M4 MIT Yes Details →
0.0.0-chat-prerelease-20260417152143 17 Apr 2026 C1 H5 M4 MIT Yes Details →
0.0.0-chat-prerelease-20260415164455 15 Apr 2026 C1 H5 M4 MIT Yes Details →
0.0.0-prerelease-20260415154507 15 Apr 2026 C1 H5 M4 MIT Yes Details →
0.0.0-chat-prerelease-20260415152704 15 Apr 2026 C1 H5 M4 MIT Yes Details →
0.0.0-prerelease-20260415152003 15 Apr 2026 C1 H5 M4 MIT Yes Details →
0.0.0-prerelease-20260415145312 15 Apr 2026 C1 H5 M4 MIT Yes Details →
0.0.0-prerelease-20260415092849 15 Apr 2026 C1 H5 M4 MIT Yes Details →
0.0.0-chat-prerelease-20260414181032 14 Apr 2026 C1 H5 M4 MIT Yes Details →
0.0.0-prerelease-20260414152623 14 Apr 2026 C1 H5 M4 MIT Yes Details →
0.0.0-chat-prerelease-20260414141814 14 Apr 2026 C1 H5 M4 MIT Yes Details →
0.0.0-next-20260414123825 14 Apr 2026 C1 H5 M4 MIT Yes Details →
0.0.0-chat-prerelease-20260413144407 13 Apr 2026 C1 H5 M4 MIT Yes Details →
4.4.4 13 Apr 2026 C1 H5 M4 MIT Yes Details →
0.0.0-chat-prerelease-20260413101648 13 Apr 2026 C1 H5 M4 MIT Yes Details →
0.0.0-chat-prerelease-20260403201229 03 Apr 2026 C1 H5 M4 MIT Yes Details →
0.0.0-chat-prerelease-20260402124815 02 Apr 2026 C1 H5 M4 MIT Yes Details →
0.0.0-chat-prerelease-20260401212829 01 Apr 2026 C1 H5 M4 — Yes Details →
0.0.0-chat-prerelease-20260401205942 01 Apr 2026 C1 H5 M4 — Yes Details →
0.0.0-prerelease-20260331093145 31 Mar 2026 C1 H5 M4 — Yes Details →
0.0.0-prerelease-20260327224514 27 Mar 2026 C1 H5 M4 — Yes Details →
0.0.0-prerelease-20260325143642 25 Mar 2026 C1 H5 M4 — Yes Details →
0.0.0-prerelease-20260324161542 24 Mar 2026 C1 H5 M4 — Yes Details →
0.0.0-prerelease-20260310150337 10 Mar 2026 C1 H5 M4 — Yes Details →
4.4.3 10 Mar 2026 C1 H5 M4 — Yes Details →
0.0.0-prerelease-20260309160514 09 Mar 2026 C1 H5 M4 — Yes Details →
0.0.0-prerelease-20260306173130 06 Mar 2026 C1 H5 M4 — Yes Details →
0.0.0-prerelease-20260306162926 06 Mar 2026 C1 H5 M4 — Yes Details →
0.0.0-prerelease-20260305183215 05 Mar 2026 C1 H5 M4 — Yes Details →
0.0.0-prerelease-20260305142821 05 Mar 2026 C1 H5 M4 — Yes Details →
0.0.0-prerelease-20260304181730 04 Mar 2026 C1 H5 M4 — Yes Details →
4.4.2 04 Mar 2026 C1 H5 M4 — Yes Details →
0.0.0-prerelease-20260302145933 02 Mar 2026 C1 H5 M4 — Yes Details →
4.4.1 20 Feb 2026 C1 H5 M4 — Yes Details →
0.0.0-prerelease-20260220162801 20 Feb 2026 C1 H5 M4 — Yes Details →
0.0.0-prerelease-20260220143958 20 Feb 2026 C1 H5 M4 — Yes Details →
4.4.0 19 Feb 2026 C1 H5 M4 — Yes Details →

The newest 120 of 634 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 10

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 10 of the 10 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for trigger.dev

The 5 most severe of 10 vulnerabilities recorded for this package

Search all 10 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Critical Vulnerability in Trigger.dev: Default Secret Authentication Flaw Exposes Sensitive Data 9.2 critical 4.5.4 02 Oct 2026
Critical Security Flaw in Trigger.dev: Unauthenticated Infrastructure Compromise via Default Secrets 8.1 high 4.5.6 02 Oct 2026
Cross-Tenant SQL Injection Vulnerability in Trigger.dev 7.7 high 4.5.6 02 Oct 2026
CVE-2026-85650: trigger.dev Server-Side Request Forgery via Unvalidated Webhook Alert-Channel URL 7.7 high 4.5.2 02 Oct 2026
Cross-Organization Task Execution Vulnerability in Trigger.dev: Missing Authentication in Run Replay Action 7.1 high 4.5.2 02 Oct 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

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

Is trigger.dev safe to use?

Vulert records 10 vulnerabilities for trigger.dev in npm: 1 critical, 5 high, 4 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is trigger.dev's Vulert package health score?

Vulert scores trigger.dev 69/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of trigger.dev affected?

No. 4.7.7, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

How many vulnerabilities does trigger.dev have?

10 vulnerabilities are recorded for trigger.dev in the npm ecosystem: 1 critical, 5 high, 4 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new trigger.dev vulnerabilities disclosed?

10 vulnerabilities were recorded for trigger.dev in the last 12 months, and the oldest entry in this database dates to 02 Oct 2026. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of trigger.dev are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

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.