VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

sequelize: vulnerability history, versions and safety

sequelize is a package in the npm ecosystem. Vulert records 17 vulnerabilities for it across 108 releases, from Oct 2017 to Aug 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
17 vulnerabilities recorded C7 H7 M3
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
2 in the last 12 months

Most recent disclosure 03 Aug 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all sequelize vulnerabilities

Vulert verdict on sequelize 6.37.8 i

Updated on 23 Oct 2026

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

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

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

  • Current release 6.37.8 — unaffected i
  • Vulnerabilities on record 17 over 8 years · 2 in the last year i
  • Latest disclosure 03 Aug 2026 i
  • Highest CVSS 10.0 i
  • With no published fix 0 i
  • Depended on by 3,643 packages i
  • Stars 30,349 i
  • OpenSSF scorecard 5/10 i
  • Last release 7 months ago i
  • Licence MIT 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 sequelize, 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
6.37.8 07 Mar 2026 none MIT — Details →
6.37.7 28 Mar 2025 H1 MIT Yes Details →
6.37.6 04 Mar 2025 H1 MIT Yes Details →
6.37.5 25 Oct 2024 H1 MIT Yes Details →
6.37.4 04 Oct 2024 H1 MIT Yes Details →
6.37.3 13 Apr 2024 C1 H1 MIT Yes Details →
6.37.2 29 Mar 2024 C1 H1 MIT Yes Details →
6.37.1 18 Feb 2024 C1 H1 MIT Yes Details →
6.37.0 11 Feb 2024 C1 H1 MIT Yes Details →
6.36.0 02 Feb 2024 C1 H1 MIT Yes Details →
6.35.2 11 Dec 2023 C1 H1 MIT Yes Details →
6.35.1 19 Nov 2023 C1 H1 MIT Yes Details →
6.35.0 12 Nov 2023 C1 H1 MIT Yes Details →
6.34.0 03 Nov 2023 C1 H1 MIT Yes Details →
6.33.0 08 Sep 2023 C1 H1 MIT Yes Details →
6.32.1 17 Jun 2023 C1 H1 MIT Yes Details →
6.32.0 01 Jun 2023 C1 H1 MIT Yes Details →
6.31.1 01 May 2023 C1 H1 MIT Yes Details →
6.31.0 09 Apr 2023 C1 H1 MIT Yes Details →
6.30.0 24 Mar 2023 C1 H1 MIT Yes Details →
6.29.3 10 Mar 2023 C1 H1 MIT Yes Details →
6.29.2 09 Mar 2023 C1 H1 MIT Yes Details →
6.29.1 07 Mar 2023 C1 H1 MIT Yes Details →
6.29.0 23 Feb 2023 C1 H1 MIT Yes Details →
6.28.2 22 Feb 2023 C1 H1 MIT Yes Details →
6.28.1 21 Feb 2023 C1 H1 MIT Yes Details →
6.28.0 20 Dec 2022 C2 H1 M1 MIT Yes Details →
6.27.0 12 Dec 2022 C2 H1 M1 MIT Yes Details →
6.26.0 29 Nov 2022 C2 H1 M1 MIT Yes Details →
6.25.8 22 Nov 2022 C2 H1 M1 MIT Yes Details →
6.25.7 19 Nov 2022 C2 H1 M1 MIT Yes Details →
6.25.6 15 Nov 2022 C2 H1 M1 MIT Yes Details →
6.25.5 07 Nov 2022 C2 H1 M1 MIT Yes Details →
6.25.4 05 Nov 2022 C2 H1 M1 MIT Yes Details →
6.25.3 19 Oct 2022 C2 H1 M1 MIT Yes Details →
6.25.2 15 Oct 2022 C2 H1 M1 MIT Yes Details →
6.25.1 13 Oct 2022 C2 H1 M1 MIT Yes Details →
6.25.0 11 Oct 2022 C2 H1 M1 MIT Yes Details →
6.24.0 04 Oct 2022 C2 H1 M1 MIT Yes Details →
6.23.2 27 Sep 2022 C2 H1 M1 MIT Yes Details →
6.23.1 22 Sep 2022 C2 H1 M1 MIT Yes Details →
6.23.0 17 Sep 2022 C2 H1 M1 MIT Yes Details →
6.22.1 16 Sep 2022 C2 H1 M1 MIT Yes Details →
6.22.0 15 Sep 2022 C2 H1 M1 MIT Yes Details →
6.21.6 09 Sep 2022 C2 H1 M1 MIT Yes Details →
6.21.5 08 Sep 2022 C2 H1 M1 MIT Yes Details →
6.21.4 18 Aug 2022 C2 H1 M1 MIT Yes Details →
6.21.3 11 Jul 2022 C2 H1 M1 MIT Yes Details →
6.21.2 28 Jun 2022 C2 H1 M1 MIT Yes Details →
6.21.1 25 Jun 2022 C2 H1 M1 MIT Yes Details →
6.21.0 16 Jun 2022 C2 H1 M1 MIT Yes Details →
6.20.1 27 May 2022 C2 H1 M1 MIT Yes Details →
6.20.0 23 May 2022 C2 H1 M1 MIT Yes Details →
6.19.2 18 May 2022 C2 H1 M1 MIT Yes Details →
6.19.1 17 May 2022 C2 H1 M1 MIT Yes Details →
6.19.0 12 Apr 2022 C3 H1 M1 MIT Yes Details →
6.18.0 03 Apr 2022 C3 H1 M1 MIT Yes Details →
6.17.0 25 Feb 2022 C3 H1 M1 MIT Yes Details →
6.16.3 24 Feb 2022 C3 H1 M1 MIT Yes Details →
6.16.2 18 Feb 2022 C3 H1 M1 MIT Yes Details →
7.0.0-alpha.9 15 Feb 2022 none MIT — Details →
7.0.0-alpha.8 11 Feb 2022 none MIT — Details →
7.0.0-alpha.7 10 Feb 2022 none MIT — Details →
6.16.1 09 Feb 2022 C3 H1 M1 MIT Yes Details →
6.16.0 08 Feb 2022 C3 H1 M1 MIT Yes Details →
7.0.0-alpha.6 07 Feb 2022 none MIT — Details →
6.15.1 06 Feb 2022 C3 H1 M1 MIT Yes Details →
6.15.0 29 Jan 2022 C3 H1 M1 MIT Yes Details →
6.14.1 25 Jan 2022 C3 H1 M1 MIT Yes Details →
6.14.0 22 Jan 2022 C3 H1 M1 MIT Yes Details →
6.13.0 10 Jan 2022 C3 H1 M1 MIT Yes Details →
7.0.0-alpha.5 04 Jan 2022 none MIT — Details →
7.0.0-alpha2.2 04 Jan 2022 none MIT — Details →
6.12.5 04 Jan 2022 C3 H1 M1 MIT Yes Details →
7.0.0-alpha2.1 04 Jan 2022 none MIT — Details →
7.0.0-alpha.4 01 Jan 2022 none MIT — Details →
6.12.4 28 Dec 2021 C3 H1 M1 MIT Yes Details →
7.0.0-alpha.3 27 Dec 2021 none MIT — Details →
6.12.3 27 Dec 2021 C3 H1 M1 MIT Yes Details →
7.0.0-alpha.2 23 Dec 2021 none MIT — Details →
7.0.0-alpha.1 23 Dec 2021 none MIT — Details →
6.12.2 22 Dec 2021 C3 H1 M1 MIT Yes Details →
5.22.5 21 Dec 2021 C3 M1 MIT Yes Details →
6.12.1 21 Dec 2021 C3 H1 M1 MIT Yes Details →
6.12.0 17 Dec 2021 C3 H1 M1 MIT Yes Details →
6.12.0-beta.3 12 Dec 2021 C3 H1 M1 MIT Yes Details →
6.12.0-beta.2 10 Dec 2021 C3 H1 M1 MIT Yes Details →
6.12.0-beta.1 04 Dec 2021 C3 H1 M1 MIT Yes Details →
6.12.0-alpha.1 19 Nov 2021 C3 H1 M1 MIT Yes Details →
6.11.0 18 Nov 2021 C3 H1 M1 MIT Yes Details →
6.10.0 18 Nov 2021 C3 H1 M1 MIT Yes Details →
6.9.0 01 Nov 2021 C3 H1 M1 MIT Yes Details →
6.8.0 24 Oct 2021 C3 H1 M1 MIT Yes Details →
6.7.0 09 Oct 2021 C3 H1 M1 MIT Yes Details →
6.6.5 06 Jul 2021 C3 H1 M1 MIT Yes Details →
6.6.4 26 Jun 2021 C3 H1 M1 MIT Yes Details →
6.6.2 23 Mar 2021 C3 H1 M1 MIT Yes Details →
6.6.1 22 Mar 2021 C3 H1 M1 MIT Yes Details →
6.6.0 21 Mar 2021 C3 H1 M1 MIT Yes Details →
5.22.4 14 Mar 2021 C3 M1 MIT Yes Details →
6.5.1 14 Mar 2021 C3 H1 M1 — Yes Details →
6.5.0 27 Jan 2021 C3 H1 M1 — Yes Details →
6.4.0 18 Jan 2021 C3 H1 M1 — Yes Details →
6.3.5 01 Sep 2020 C3 H1 M1 — Yes Details →
6.3.4 01 Aug 2020 C3 H1 M1 — Yes Details →
6.3.3 11 Jul 2020 C3 H1 M1 — Yes Details →
6.3.2 11 Jul 2020 C3 H1 M1 — Yes Details →
6.3.1 10 Jul 2020 C3 H1 M1 — Yes Details →
6.3.0 04 Jul 2020 C3 H1 M1 — Yes Details →
6.2.4 01 Jul 2020 C3 H1 M1 — Yes Details →
5.22.3 30 Jun 2020 C3 M1 — Yes Details →
6.2.3 28 Jun 2020 C3 H1 M1 — Yes Details →
6.2.2 27 Jun 2020 C3 H1 M1 — Yes Details →
6.2.1 27 Jun 2020 C3 H1 M1 — Yes Details →
5.22.2 27 Jun 2020 C3 M1 — Yes Details →
6.2.0 26 Jun 2020 C3 H1 M1 — Yes Details →
5.22.1 26 Jun 2020 C3 M1 — Yes Details →
6.1.1 26 Jun 2020 C3 H1 M1 — Yes Details →
6.1.0 24 Jun 2020 C3 H1 M1 — Yes Details →
5.22.0 24 Jun 2020 C3 M1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2017 1
  • 2019 9
  • 2020 2
  • 2023 3
  • 2026 2

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

03 Vulnerabilities

Recorded vulnerabilities for sequelize

The 5 most severe of 17 vulnerabilities recorded for this package

Search all 17 in the database →
Vulnerability Severity Fixed version ↑ Disclosed ↑
CVE-2023-25813: Sequelize SQL Injection via Replacements 10.0 critical 6.19.1 22 Feb 2023
CVE-2023-22579: Unsafe fall-through in getWhereConditions in Sequelize 9.9 critical 6.28.1 23 Feb 2023
CVE-2026-69240: Sequelize SQL Injection Vulnerability in Oracle DB 9.8 critical 6.37.4 03 Aug 2026
CVE-2019-10752: SQL Injection in sequelize 9.8 critical 4.44.3 25 Oct 2019
CVE-2016-1000225: SQL Injection via GeoJSON in sequelize 9.8 critical 3.23.6 01 Sep 2020

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 sequelize

Is sequelize safe to use?

Vulert records 17 vulnerabilities for sequelize in npm: 7 critical, 7 high, 3 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 sequelize's Vulert package health score?

Vulert scores sequelize 77/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 sequelize affected?

No. 6.37.8, 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 sequelize should I use?

6.37.8 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 sequelize have?

17 vulnerabilities are recorded for sequelize in the npm ecosystem: 7 critical, 7 high, 3 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 sequelize vulnerabilities disclosed?

2 vulnerabilities were recorded for sequelize in the last 12 months, and the oldest entry in this database dates to 24 Oct 2017. 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 sequelize 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 sequelize for upcoming vulnerabilities?

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