VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@novu/js: vulnerability history, versions and safety

@novu/js is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 77 releases, first recorded in Sep 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded M1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
1 in the last 12 months

Most recent disclosure 22 Sep 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all @novu/js vulnerabilities

Vulert verdict on @novu/js 3.19.2 i

Updated on 23 Oct 2026

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

Package health score 90/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Active

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

  • Current release 3.19.2 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 1 in the last year i
  • Latest disclosure 22 Sep 2026 i
  • Highest CVSS 5.1 i
  • With no published fix 0 i
  • Depended on by 6 packages i
  • Stars 40,152 i
  • Last release 1 month ago i
  • Licence ISC i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 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 @novu/js, 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
3.20.0-rc.569d407fd0 24 Sep 2026 none ISC — Details →
3.19.2 07 Sep 2026 none ISC — Details →
3.19.2-rc.dc9caee828 04 Sep 2026 none ISC — Details →
3.19.1 31 Aug 2026 none ISC — Details →
3.19.1-rc.56a8a168f8 28 Aug 2026 none ISC — Details →
3.19.1-rc.852194fa77 25 Aug 2026 none ISC — Details →
3.19.1-rc.68f5589d4e 21 Aug 2026 none ISC — Details →
3.20.0-rc.d57e78e026 14 Aug 2026 none ISC — Details →
3.19.0 07 Aug 2026 none ISC — Details →
3.18.2 04 Aug 2026 none ISC — Details →
3.18.1 23 Jul 2026 none ISC — Details →
3.18.0 08 Jul 2026 none ISC — Details →
3.17.1-rc.1-rc.da35e9062d 06 Jul 2026 M1 ISC Yes Details →
3.17.0 01 Jun 2026 M1 ISC Yes Details →
3.17.0-rc.d0046861c6 01 Jun 2026 M1 ISC Yes Details →
3.16.0 27 Apr 2026 M1 ISC Yes Details →
3.15.0 13 Apr 2026 M1 ISC Yes Details →
3.15.0-rc.cd43306f31 13 Apr 2026 M1 ISC Yes Details →
3.14.1 27 Feb 2026 M1 ISC Yes Details →
3.14.1-rc.4ba98f00f2 27 Feb 2026 M1 ISC Yes Details →
3.14.0 12 Feb 2026 M1 ISC Yes Details →
3.13.0 28 Jan 2026 M1 ISC Yes Details →
3.13.0-nightly.20260127.b5d91bd556 27 Jan 2026 M1 ISC Yes Details →
3.12.0 07 Jan 2026 M1 ISC Yes Details →
3.11.2 24 Dec 2025 M1 ISC Yes Details →
3.11.2-nightly.20251224.bd7e795b82 24 Dec 2025 M1 ISC Yes Details →
3.11.2-nightly.20251224.97b30e30dd 24 Dec 2025 M1 ISC Yes Details →
3.11.2-nightly.20251224.eb609546a3 24 Dec 2025 M1 ISC Yes Details →
3.11.1 23 Dec 2025 M1 ISC Yes Details →
3.12.0-rc.2 12 Dec 2025 M1 ISC Yes Details →
3.12.0-rc.1 12 Dec 2025 M1 ISC Yes Details →
3.11.0 27 Oct 2025 M1 ISC Yes Details →
3.11.0-rc.1 24 Oct 2025 M1 ISC Yes Details →
3.8.2 03 Oct 2025 M1 ISC Yes Details →
3.7.1 03 Oct 2025 M1 ISC Yes Details →
3.10.1 22 Sep 2025 M1 ISC Yes Details →
3.10.0 22 Sep 2025 M1 ISC Yes Details →
3.9.3 03 Sep 2025 M1 ISC Yes Details →
3.9.2 03 Sep 2025 M1 ISC Yes Details →
3.9.1 27 Aug 2025 M1 ISC Yes Details →
3.8.1 13 Aug 2025 M1 ISC Yes Details →
3.8.1-nightly.20250813.c22578f1f8 13 Aug 2025 M1 ISC Yes Details →
3.8.1-nightly.20250813.014483f9e1 13 Aug 2025 M1 ISC Yes Details →
3.8.1-nightly.20250813.b0350eac88 13 Aug 2025 M1 ISC Yes Details →
3.8.0 11 Aug 2025 M1 ISC Yes Details →
3.7.1-nightly.20250723 23 Jul 2025 M1 ISC Yes Details →
3.7.0 22 Jul 2025 M1 ISC Yes Details →
3.6.0-nightly.20250720 20 Jul 2025 M1 ISC Yes Details →
3.6.0 14 Jul 2025 M1 ISC Yes Details →
3.6.0-nightly.20250627 27 Jun 2025 M1 ISC Yes Details →
3.5.1-nightly.20250610 10 Jun 2025 M1 ISC Yes Details →
3.5.0 27 May 2025 M1 ISC Yes Details →
3.5.0-rc.3 22 May 2025 M1 ISC Yes Details →
3.5.0-rc.2 21 May 2025 M1 ISC Yes Details →
3.5.0-rc.1 21 May 2025 M1 ISC Yes Details →
3.4.0 16 May 2025 M1 ISC Yes Details →
3.3.1 07 May 2025 M1 ISC Yes Details →
3.3.0 07 May 2025 M1 ISC Yes Details →
3.2.0 30 Apr 2025 M1 ISC Yes Details →
3.1.0 11 Apr 2025 M1 ISC Yes Details →
3.0.3 31 Mar 2025 M1 ISC Yes Details →
3.0.1 24 Mar 2025 M1 ISC Yes Details →
3.0.0 17 Mar 2025 M1 ISC Yes Details →
3.0.0-canary.2 17 Mar 2025 M1 ISC Yes Details →
3.0.0-canary.1 17 Mar 2025 M1 ISC Yes Details →
3.0.0-canary.0 17 Mar 2025 M1 ISC Yes Details →
2.6.6 25 Feb 2025 M1 ISC Yes Details →
2.6.5 07 Feb 2025 M1 ISC Yes Details →
2.6.4 24 Dec 2024 M1 ISC Yes Details →
2.6.3 26 Nov 2024 M1 ISC Yes Details →
2.6.1 19 Nov 2024 M1 ISC Yes Details →
2.6.0 31 Oct 2024 M1 ISC Yes Details →
2.5.0 15 Oct 2024 M1 ISC Yes Details →
2.4.0 07 Oct 2024 M1 ISC Yes Details →
2.3.1 03 Oct 2024 M1 ISC Yes Details →
2.3.0 25 Sep 2024 M1 ISC Yes Details →
2.2.1 19 Sep 2024 M1 ISC Yes Details →
2.2.0 19 Sep 2024 M1 ISC Yes Details →
2.1.2 17 Sep 2024 M1 ISC Yes Details →
2.1.1 16 Sep 2024 M1 ISC Yes Details →
2.1.0 12 Sep 2024 M1 ISC Yes Details →
2.0.1 10 Sep 2024 M1 ISC Yes Details →
2.0.0 10 Sep 2024 M1 ISC Yes Details →
2.0.0-canary.2 29 Aug 2024 M1 ISC Yes Details →
2.0.0-canary.1 23 Aug 2024 M1 ISC Yes Details →
2.0.0-canary.0 07 Aug 2024 M1 ISC Yes Details →
2.0.0-alpha.2 07 Aug 2024 M1 ISC Yes Details →
2.0.0-alpha.1 07 Aug 2024 M1 ISC Yes Details →
2.0.0-alpha.0 07 Aug 2024 M1 ISC Yes Details →

All 89 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for @novu/js

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-75510: Novu Stored XSS Vulnerability via Notification Redirect URL 5.1 medium 3.18.0 22 Sep 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: 23/Oct/2026 · Vulnerabilities in our DB: 524315

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 @novu/js

Is @novu/js safe to use?

Vulert records 1 vulnerabilities for @novu/js in npm: 0 critical, 0 high, 1 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 @novu/js's Vulert package health score?

Vulert scores @novu/js 90/100, which reads as healthy. 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 @novu/js affected?

No. 3.19.2, 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.

Which version of @novu/js should I use?

3.19.2 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does @novu/js have?

1 vulnerability is recorded for @novu/js in the npm ecosystem: 0 critical, 0 high, 1 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 @novu/js vulnerabilities disclosed?

1 vulnerability was recorded for @novu/js in the last 12 months, and the oldest entry in this database dates to 22 Sep 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 @novu/js 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 @novu/js for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the @novu/js version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.