VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

unleash-server: vulnerability history, versions and safety

unleash-server is a package in the npm ecosystem. Vulert records 7 vulnerabilities for it across 116 releases, from Aug 2026 to 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
7 vulnerabilities recorded H2 M4 L1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
7 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 unleash-server vulnerabilities

Vulert verdict on unleash-server 8.2.1 i

Updated on 23 Oct 2026

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

Package health score 76/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

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

  • Current release 8.2.1 — unaffected i
  • Vulnerabilities on record 7 over 1 year · 7 in the last year i
  • Latest disclosure 22 Sep 2026 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Stars 13,885 i
  • OpenSSF scorecard 5/10 i
  • Last release this month i
  • Licence AGPL-3.0-or-later 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 unleash-server, 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
8.2.1 22 Oct 2026 none AGPL-3.0-or-later — Details →
8.2.0 08 Sep 2026 none AGPL-3.0-or-later — Details →
8.1.0 05 Aug 2026 none AGPL-3.0-or-later — Details →
8.0.3 10 Jul 2026 none AGPL-3.0-or-later — Details →
7.5.2 29 Jun 2026 H1 M3 L1 Apache-2.0 Yes Details →
7.6.5 29 Jun 2026 H1 M3 L1 Apache-2.0 Yes Details →
8.0.2 29 Jun 2026 H1 M3 L1 AGPL-3.0-or-later Yes Details →
8.0.1 16 Jun 2026 H1 M3 L1 AGPL-3.0-or-later Yes Details →
8.0.0 09 Jun 2026 H1 M3 L1 AGPL-3.0-or-later Yes Details →
7.6.5-beta.2 02 Jun 2026 H1 M3 L1 AGPL-3.0-or-later Yes Details →
7.6.5-beta.1 01 Jun 2026 H1 M3 L1 AGPL-3.0-or-later Yes Details →
7.6.5-beta.0 14 May 2026 H1 M3 L1 Apache-2.0 Yes Details →
7.6.4 14 May 2026 H1 M3 L1 Apache-2.0 Yes Details →
7.6.3 15 Apr 2026 H1 M3 L1 Apache-2.0 Yes Details →
7.6.2 15 Apr 2026 H1 M3 L1 Apache-2.0 Yes Details →
7.6.1 09 Apr 2026 H1 M3 L1 Apache-2.0 Yes Details →
7.5.1 10 Mar 2026 H2 M4 L1 Apache-2.0 Yes Details →
7.5.0 04 Mar 2026 H2 M4 L1 Apache-2.0 Yes Details →
7.4.3 27 Feb 2026 H2 M4 L1 Apache-2.0 Yes Details →
7.4.2 25 Feb 2026 H2 M4 L1 Apache-2.0 Yes Details →
7.4.1 05 Feb 2026 H2 M4 L1 Apache-2.0 Yes Details →
7.4.0 12 Dec 2025 H2 M4 L1 Apache-2.0 Yes Details →
7.3.0 07 Nov 2025 H2 M4 L1 Apache-2.0 Yes Details →
7.2.3 16 Oct 2025 H2 M4 L1 Apache-2.0 Yes Details →
7.2.2 24 Sep 2025 H2 M4 L1 Apache-2.0 Yes Details →
7.2.1 18 Sep 2025 H2 M4 L1 Apache-2.0 Yes Details →
7.2.0 03 Sep 2025 H2 M4 L1 Apache-2.0 Yes Details →
7.1.2 28 Aug 2025 H2 M4 L1 Apache-2.0 Yes Details →
7.1.1 26 Aug 2025 H2 M4 L1 Apache-2.0 Yes Details →
7.1.0 13 Aug 2025 H2 M4 L1 Apache-2.0 Yes Details →
7.0.6 25 Jul 2025 H2 M4 L1 Apache-2.0 Yes Details →
7.0.5 24 Jul 2025 H2 M4 L1 Apache-2.0 Yes Details →
7.0.4 02 Jul 2025 H2 M4 L1 Apache-2.0 Yes Details →
7.0.3 17 Jun 2025 H2 M4 L1 Apache-2.0 Yes Details →
7.0.2 17 Jun 2025 H2 M4 L1 Apache-2.0 Yes Details →
7.0.1 13 Jun 2025 H2 M4 L1 Apache-2.0 Yes Details →
7.0.0 11 Jun 2025 H2 M4 L1 Apache-2.0 Yes Details →
6.10.1 02 Jun 2025 H2 M4 L1 Apache-2.0 Yes Details →
6.10.0 07 May 2025 H2 M4 L1 Apache-2.0 Yes Details →
6.9.2 29 Apr 2025 H2 M4 L1 Apache-2.0 Yes Details →
6.9.1 10 Apr 2025 H2 M4 L1 Apache-2.0 Yes Details →
6.9.0 02 Apr 2025 H2 M4 L1 Apache-2.0 Yes Details →
6.8.0 06 Mar 2025 H2 M4 L1 Apache-2.0 Yes Details →
6.7.2 19 Feb 2025 H2 M4 L1 Apache-2.0 Yes Details →
6.7.1 11 Feb 2025 H2 M4 L1 Apache-2.0 Yes Details →
6.7.0 11 Feb 2025 H2 M4 L1 Apache-2.0 Yes Details →
6.6.0 14 Jan 2025 H2 M4 L1 Apache-2.0 Yes Details →
6.5.3 19 Dec 2024 H2 M4 L1 Apache-2.0 Yes Details →
6.5.2 13 Dec 2024 H2 M4 L1 Apache-2.0 Yes Details →
6.5.1 12 Dec 2024 H2 M4 L1 Apache-2.0 Yes Details →
6.5.0 28 Nov 2024 H2 M4 L1 Apache-2.0 Yes Details →
6.4.1 31 Oct 2024 H2 M4 L1 Apache-2.0 Yes Details →
6.4.0 30 Oct 2024 H2 M4 L1 Apache-2.0 Yes Details →
6.3.0 01 Oct 2024 H2 M4 L1 Apache-2.0 Yes Details →
6.2.4 19 Sep 2024 H2 M4 L1 Apache-2.0 Yes Details →
6.2.3 18 Sep 2024 H2 M4 L1 Apache-2.0 Yes Details →
6.2.2 16 Sep 2024 H2 M4 L1 Apache-2.0 Yes Details →
6.2.1 11 Sep 2024 H2 M4 L1 Apache-2.0 Yes Details →
6.2.0 05 Sep 2024 H2 M4 L1 Apache-2.0 Yes Details →
6.1.12 22 Aug 2024 H2 M4 L1 Apache-2.0 Yes Details →
6.0.7 22 Aug 2024 H2 M4 L1 Apache-2.0 Yes Details →
5.12.8 22 Aug 2024 H2 M4 L1 Apache-2.0 Yes Details →
6.1.11 21 Aug 2024 H2 M4 L1 Apache-2.0 Yes Details →
6.1.10 16 Aug 2024 H2 M4 L1 Apache-2.0 Yes Details →
6.1.9 14 Aug 2024 H2 M4 L1 Apache-2.0 Yes Details →
6.1.8 14 Aug 2024 H2 M4 L1 Apache-2.0 Yes Details →
6.1.7 14 Aug 2024 H2 M4 L1 Apache-2.0 Yes Details →
6.1.6 14 Aug 2024 H2 M4 L1 Apache-2.0 Yes Details →
6.1.5 13 Aug 2024 H2 M4 L1 Apache-2.0 Yes Details →
6.1.4 13 Aug 2024 H2 M4 L1 Apache-2.0 Yes Details →
6.1.3 13 Aug 2024 H2 M4 L1 Apache-2.0 Yes Details →
6.1.2 08 Aug 2024 H2 M4 L1 Apache-2.0 Yes Details →
6.1.0 07 Aug 2024 H2 M4 L1 Apache-2.0 Yes Details →
6.0.6 03 Jul 2024 H2 M4 L1 Apache-2.0 Yes Details →
6.0.5 03 Jul 2024 H2 M4 L1 Apache-2.0 Yes Details →
6.0.4 19 Jun 2024 H2 M4 L1 Apache-2.0 Yes Details →
6.0.3 14 Jun 2024 H2 M4 L1 Apache-2.0 Yes Details →
6.0.2 12 Jun 2024 H2 M4 L1 Apache-2.0 Yes Details →
6.0.1 10 Jun 2024 H2 M4 L1 Apache-2.0 Yes Details →
6.0.0 06 Jun 2024 H2 M4 L1 Apache-2.0 Yes Details →
5.12.7 04 Jun 2024 H2 M4 L1 Apache-2.0 Yes Details →
5.12.5 03 Jun 2024 H2 M4 L1 Apache-2.0 Yes Details →
5.12.4 17 May 2024 H2 M4 L1 Apache-2.0 Yes Details →
5.12.3 16 May 2024 H2 M4 L1 Apache-2.0 Yes Details →
5.12.2 08 May 2024 H2 M4 L1 Apache-2.0 Yes Details →
5.12.1 06 May 2024 H2 M4 L1 Apache-2.0 Yes Details →
5.12.0 02 May 2024 H2 M4 L1 Apache-2.0 Yes Details →
5.11.3 18 Apr 2024 H2 M4 L1 Apache-2.0 Yes Details →
5.11.2 12 Apr 2024 H2 M4 L1 Apache-2.0 Yes Details →
5.11.1 09 Apr 2024 H2 M4 L1 Apache-2.0 Yes Details →
5.11.0 05 Apr 2024 H2 M4 L1 Apache-2.0 Yes Details →
5.10.2 21 Mar 2024 H2 M4 L1 Apache-2.0 Yes Details →
5.10.1 12 Mar 2024 H2 M4 L1 Apache-2.0 Yes Details →
5.10.0 05 Mar 2024 H2 M4 L1 Apache-2.0 Yes Details →
5.9.6 21 Feb 2024 H2 M4 L1 Apache-2.0 Yes Details →
5.9.5 19 Feb 2024 H2 M4 L1 Apache-2.0 Yes Details →
5.9.4 16 Feb 2024 H2 M4 L1 Apache-2.0 Yes Details →
5.7.3 16 Feb 2024 H2 M4 L1 Apache-2.0 Yes Details →
5.9.3 06 Feb 2024 H2 M4 L1 Apache-2.0 Yes Details →
5.9.2 05 Feb 2024 H2 M4 L1 Apache-2.0 Yes Details →
5.9.1 02 Feb 2024 H2 M4 L1 — Yes Details →
5.9.0 01 Feb 2024 H2 M4 L1 — Yes Details →
5.8.2 19 Jan 2024 H2 M4 L1 — Yes Details →
5.8.1 10 Jan 2024 H2 M4 L1 — Yes Details →
5.8.0 05 Jan 2024 H2 M4 L1 — Yes Details →
5.7.2 21 Dec 2023 H2 M4 L1 — Yes Details →
5.7.1 19 Dec 2023 H2 M4 L1 — Yes Details →
5.7.0 30 Nov 2023 H2 M4 L1 — Yes Details →
5.6.10 28 Nov 2023 H2 M4 L1 — Yes Details →
5.6.9 21 Nov 2023 H2 M4 L1 — Yes Details →
5.6.8 16 Nov 2023 H2 M4 L1 — Yes Details →
5.6.7 15 Nov 2023 H2 M4 L1 — Yes Details →
5.6.6 10 Nov 2023 H2 M4 L1 — Yes Details →
5.6.5 09 Nov 2023 H2 M4 L1 — Yes Details →
5.6.4 03 Nov 2023 H2 M4 L1 — Yes Details →
5.6.3 03 Nov 2023 H2 M4 L1 — Yes Details →
5.6.2 01 Nov 2023 H2 M4 L1 — Yes Details →
5.6.1 30 Oct 2023 H2 M4 L1 — Yes Details →
5.6.0 26 Oct 2023 H2 M4 L1 — Yes Details →
5.5.7 20 Oct 2023 H2 M4 L1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 7

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

03 Vulnerabilities

Recorded vulnerabilities for unleash-server

The 5 most severe of 7 vulnerabilities recorded for this package

Search all 7 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-63462: Unleash Server Unauthenticated DoS via OpenAPI Validation Error 7.5 high 7.5.2 21 Aug 2026
CVE-2026-77426: Unleash Server Critical Permission Bypass and Cross-Project Data Exposure 7.1 high 8.0.3 22 Sep 2026
CVE-2026-63004: Unleash Server SSRF Vulnerability in Webhook Addon 5.5 medium 7.5.2 21 Aug 2026
CVE-2026-76910: Unleash Server Allows Unauthorized Feature Cloning Across Projects 5.3 medium 8.0.3 22 Sep 2026
CVE-2026-77425: Unleash Server Cross-Project Integrity Write Vulnerability 4.3 medium 8.0.3 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 unleash-server

Is unleash-server safe to use?

Vulert records 7 vulnerabilities for unleash-server in npm: 0 critical, 2 high, 4 medium and 1 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 unleash-server's Vulert package health score?

Vulert scores unleash-server 76/100, which reads as in good shape. 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 unleash-server affected?

No. 8.2.1, 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 unleash-server have?

7 vulnerabilities are recorded for unleash-server in the npm ecosystem: 0 critical, 2 high, 4 medium and 1 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new unleash-server vulnerabilities disclosed?

7 vulnerabilities were recorded for unleash-server in the last 12 months, and the oldest entry in this database dates to 21 Aug 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 unleash-server 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 unleash-server for upcoming vulnerabilities?

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