VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

feathers-sequelize: vulnerability history, versions and safety

feathers-sequelize is a package in the npm ecosystem. Vulert records 3 vulnerabilities for it across 9 releases, first recorded in Oct 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded C3
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all feathers-sequelize vulnerabilities

Vulert verdict on feathers-sequelize 7.0.3 i

Updated on 23 Oct 2026

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

Package health score 59/100
  • Security Some issues to review
  • Maintenance Maintaining
  • Popularity Niche
  • Community Quiet

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

  • Current release 7.0.3 — unaffected i
  • Vulnerabilities on record 3 over 1 year · 0 in the last year i
  • Latest disclosure 26 Oct 2022 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Depended on by 14 packages i
  • Stars 208 i
  • OpenSSF scorecard 2/10 i
  • Last release 35 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 feathers-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
8.0.0-pre.3 04 May 2025 none MIT — Details →
8.0.0-pre.2 12 Mar 2025 none MIT — Details →
8.0.0-pre.1 13 May 2024 none MIT — Details →
8.0.0-pre.0 12 May 2024 none MIT — Details →
7.0.3 01 Nov 2023 none MIT — Details →
7.0.2 21 Jun 2023 none MIT — Details →
7.0.1 03 Apr 2023 none MIT — Details →
7.0.0 24 Feb 2023 none MIT — Details →
7.0.0-pre.1 06 Jan 2023 none MIT — Details →
6.4.0 15 Nov 2022 none MIT — Details →
6.3.6 26 Oct 2022 none MIT — Details →
7.0.0-pre.0 04 Oct 2022 none MIT — Details →
6.3.4 08 Jun 2022 none MIT — Details →
6.3.3 13 Apr 2022 C2 MIT Yes Details →
6.3.2 19 Oct 2021 C3 MIT Yes Details →
6.3.1 14 Oct 2021 C3 MIT Yes Details →
6.3.0 14 Oct 2021 C3 MIT Yes Details →
6.2.0 29 Apr 2020 C3 MIT Yes Details →
6.1.0 07 Oct 2019 C3 MIT Yes Details →
6.0.2 29 Sep 2019 C3 MIT Yes Details →
6.0.1 22 Jul 2019 C3 MIT Yes Details →
6.0.0 06 Jul 2019 C3 MIT Yes Details →
5.1.3 18 Apr 2019 none MIT — Details →
5.1.2 17 Apr 2019 none MIT — Details →
5.1.1 09 Apr 2019 none MIT — Details →
5.1.0 05 Apr 2019 none MIT — Details →
5.0.1 30 Mar 2019 none MIT — Details →
5.0.0 30 Mar 2019 none MIT — Details →
4.1.1 27 Feb 2019 none MIT — Details →
4.1.0 25 Jan 2019 none MIT — Details →
4.0.8 10 Jan 2019 none MIT — Details →
4.0.7 29 Dec 2018 none MIT — Details →
4.0.6 27 Dec 2018 none MIT — Details →
4.0.5 26 Dec 2018 none MIT — Details →
4.0.4 22 Dec 2018 none MIT — Details →
4.0.3 21 Dec 2018 none MIT — Details →
4.0.2 21 Dec 2018 none MIT — Details →
4.0.1 21 Dec 2018 none MIT — Details →
4.0.0 20 Dec 2018 none MIT — Details →
3.1.3 29 Oct 2018 none MIT — Details →
3.1.2 07 Jun 2018 none MIT — Details →
3.1.1 03 Jun 2018 none MIT — Details →
3.1.0 27 Mar 2018 none MIT — Details →
3.0.2 25 Mar 2018 none MIT — Details →
3.0.1 07 Mar 2018 none MIT — Details →
3.0.0 04 Dec 2017 none MIT — Details →
2.4.0 06 Nov 2017 none MIT — Details →
2.3.2 14 Oct 2017 none MIT — Details →
2.3.1 06 Sep 2017 none MIT — Details →
2.3.0 19 Aug 2017 none MIT — Details →
2.2.1 08 Aug 2017 none MIT — Details →
2.2.0 24 Jul 2017 none MIT — Details →
2.1.0 13 Jul 2017 none MIT — Details →
2.0.1 09 Jun 2017 none MIT — Details →
2.0.0 03 May 2017 none MIT — Details →
1.4.5 26 Mar 2017 none MIT — Details →
1.4.4 24 Mar 2017 none MIT — Details →
1.4.3 17 Mar 2017 none MIT — Details →
1.4.2 14 Mar 2017 none MIT — Details →
1.4.1 10 Mar 2017 none MIT — Details →
1.4.0 11 Nov 2016 none MIT — Details →
1.3.3 28 Sep 2016 none MIT — Details →
1.3.2 25 Aug 2016 none MIT — Details →
1.3.1 20 Jul 2016 none MIT — Details →
1.3.0 08 Jul 2016 none MIT — Details →
1.2.0 17 Jun 2016 none MIT — Details →
1.1.6 15 Jun 2016 none MIT — Details →
1.1.5 10 Jun 2016 none MIT — Details →
1.1.4 10 Mar 2016 none MIT — Details →
1.1.3 09 Mar 2016 none MIT — Details →
1.1.2 24 Feb 2016 none MIT — Details →
1.1.1 02 Feb 2016 none MIT — Details →
1.1.0 30 Jan 2016 none MIT — Details →
1.0.10 24 Jan 2016 none MIT — Details →
1.0.9 11 Jan 2016 none MIT — Details →
1.0.7 06 Jan 2016 none MIT — Details →
1.0.6 29 Dec 2015 none MIT — Details →
1.0.5 21 Dec 2015 none MIT — Details →
1.0.4 21 Dec 2015 none MIT — Details →
1.0.3 21 Dec 2015 none MIT — Details →
1.0.2 21 Dec 2015 none MIT — Details →
1.0.1 19 Dec 2015 none MIT — Details →
1.0.0 19 Dec 2015 none MIT — Details →
0.2.1 18 Dec 2015 none MIT — Details →
0.2.0 13 Dec 2015 none MIT — Details →
0.1.0 23 Nov 2015 none MIT — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 3

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

03 Vulnerabilities

Recorded vulnerabilities for feathers-sequelize

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2022-29822: feathers-sequelize SQL Injection Vulnerability 9.8 critical 6.3.4 26 Oct 2022
CVE-2022-29823: Feather-Sequelize cleanQuery method vulnerable to Prototype Pollution 9.8 critical 6.3.3 26 Oct 2022
CVE-2022-2422: SQL Injection in feathers-sequelize 9.8 critical 6.3.4 26 Oct 2022

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 feathers-sequelize

Is feathers-sequelize safe to use?

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

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

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

7.0.3 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 feathers-sequelize have?

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

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

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the feathers-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.