VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

mongoose: vulnerability history, versions and safety

mongoose is a package in the npm ecosystem. Vulert records 10 vulnerabilities for it across 3 releases, from Oct 2019 to Jul 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 C4 H4 M2
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 24 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all mongoose vulnerabilities

Vulert verdict on mongoose 9.11.3 i

Updated on 22 Oct 2026

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

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

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

  • Current release 9.11.3 — unaffected i
  • Vulnerabilities on record 10 over 6 years · 2 in the last year i
  • Latest disclosure 24 Jul 2026 i
  • Highest CVSS 10.0 i
  • With no published fix 0 i
  • Depended on by 1,583 packages i
  • Stars 27,456 i
  • OpenSSF scorecard 5/10 i
  • Last release this month 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 mongoose, 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
9.11.3 21 Oct 2026 none MIT — Details →
8.24.6 20 Oct 2026 none MIT — Details →
9.11.2 12 Oct 2026 none MIT — Details →
9.11.1 07 Oct 2026 none MIT — Details →
9.11.0 05 Oct 2026 none MIT — Details →
8.24.5 04 Oct 2026 none MIT — Details →
9.10.4 03 Oct 2026 none MIT — Details →
9.10.3 29 Sep 2026 none MIT — Details →
9.10.2 22 Sep 2026 none MIT — Details →
9.10.1 14 Sep 2026 none MIT — Details →
9.10.0 10 Sep 2026 none MIT — Details →
9.9.5 04 Sep 2026 none MIT — Details →
9.9.4 25 Aug 2026 none MIT — Details →
8.24.4 21 Aug 2026 none MIT — Details →
9.9.3 17 Aug 2026 none MIT — Details →
6.13.11 10 Aug 2026 none MIT — Details →
7.8.12 10 Aug 2026 none MIT — Details →
8.24.3 10 Aug 2026 none MIT — Details →
9.9.2 10 Aug 2026 none MIT — Details →
9.9.1 31 Jul 2026 none MIT — Details →
9.9.0 30 Jul 2026 none MIT — Details →
8.24.2 27 Jul 2026 none MIT — Details →
9.8.1 27 Jul 2026 none MIT — Details →
9.8.0 20 Jul 2026 none MIT — Details →
7.8.11 06 Jul 2026 none MIT — Details →
9.7.4 06 Jul 2026 none MIT — Details →
9.7.3 26 Jun 2026 none MIT — Details →
6.13.10 22 Jun 2026 none MIT — Details →
7.8.10 22 Jun 2026 none MIT — Details →
8.24.1 22 Jun 2026 none MIT — Details →
9.7.2 22 Jun 2026 none MIT — Details →
9.7.1 17 Jun 2026 none MIT — Details →
9.7.0 09 Jun 2026 none MIT — Details →
9.6.3 27 May 2026 none MIT — Details →
8.24.0 14 May 2026 none MIT — Details →
9.6.2 08 May 2026 none MIT — Details →
9.6.1 29 Apr 2026 none MIT — Details →
9.6.0 28 Apr 2026 none MIT — Details →
8.23.1 23 Apr 2026 none MIT — Details →
9.5.0 20 Apr 2026 none MIT — Details →
9.4.1 03 Apr 2026 none MIT — Details →
9.4.0 03 Apr 2026 none MIT — Details →
9.3.3 25 Mar 2026 none MIT — Details →
9.3.2 23 Mar 2026 none MIT — Details →
9.3.1 17 Mar 2026 none MIT — Details →
9.3.0 10 Mar 2026 none MIT — Details →
9.2.4 04 Mar 2026 none MIT — Details →
9.2.3 26 Feb 2026 none MIT — Details →
9.2.2 23 Feb 2026 none MIT — Details →
9.2.1 11 Feb 2026 none MIT — Details →
9.2.0 09 Feb 2026 none MIT — Details →
8.23.0 09 Feb 2026 none MIT — Details →
9.1.6 04 Feb 2026 none MIT — Details →
8.22.1 04 Feb 2026 none MIT — Details →
7.8.9 04 Feb 2026 none MIT — Details →
6.13.9 04 Feb 2026 M1 MIT Yes Details →
8.22.0 27 Jan 2026 none MIT — Details →
8.21.1 23 Jan 2026 none MIT — Details →
9.1.5 20 Jan 2026 none MIT — Details →
9.1.4 16 Jan 2026 none MIT — Details →
9.1.3 11 Jan 2026 none MIT — Details →
9.1.2 05 Jan 2026 none MIT — Details →
9.1.1 30 Dec 2025 none MIT — Details →
9.1.0 29 Dec 2025 none MIT — Details →
8.21.0 29 Dec 2025 none MIT — Details →
8.20.4 18 Dec 2025 none MIT — Details →
9.0.2 17 Dec 2025 none MIT — Details →
8.20.3 15 Dec 2025 none MIT — Details →
9.0.1 05 Dec 2025 none MIT — Details →
8.20.2 05 Dec 2025 none MIT — Details →
7.8.8 05 Dec 2025 none MIT — Details →
9.0.0 21 Nov 2025 none MIT — Details →
8.20.1 20 Nov 2025 none MIT — Details →
9.0.0-rc1 19 Nov 2025 none MIT — Details →
9.0.0-rc0 19 Nov 2025 none MIT — Details →
8.20.0 17 Nov 2025 none MIT — Details →
8.19.4 14 Nov 2025 none MIT — Details →
8.19.3 04 Nov 2025 none MIT — Details →
8.19.2 20 Oct 2025 none MIT — Details →
8.19.1 06 Oct 2025 none MIT — Details →
8.19.0 02 Oct 2025 none MIT — Details →
8.18.3 29 Sep 2025 none MIT — Details →
8.18.2 22 Sep 2025 none MIT — Details →
8.18.1 08 Sep 2025 none MIT — Details →
8.18.0 22 Aug 2025 none MIT — Details →
8.17.2 18 Aug 2025 none MIT — Details →
8.17.1 07 Aug 2025 none MIT — Details →
8.17.0 30 Jul 2025 none MIT — Details →
8.16.5 25 Jul 2025 none MIT — Details →
8.16.4 16 Jul 2025 none MIT — Details →
8.16.3 10 Jul 2025 none MIT — Details →
8.16.2 07 Jul 2025 none MIT — Details →
8.16.1 26 Jun 2025 none MIT — Details →
8.16.0 16 Jun 2025 none MIT — Details →
8.15.2 12 Jun 2025 none MIT — Details →
8.15.1 26 May 2025 none MIT — Details →
8.15.0 16 May 2025 none MIT — Details →
8.14.3 13 May 2025 none MIT — Details →
8.14.2 08 May 2025 none MIT — Details →
7.8.7 30 Apr 2025 none MIT — Details →
8.14.1 29 Apr 2025 none — — Details →
8.14.0 25 Apr 2025 none — — Details →
8.13.3 24 Apr 2025 none — — Details →
8.13.2 03 Apr 2025 none — — Details →
8.13.1 28 Mar 2025 none — — Details →
8.13.0 24 Mar 2025 none — — Details →
8.12.2 21 Mar 2025 none — — Details →
8.12.1 04 Mar 2025 none — — Details →
8.12.0 03 Mar 2025 none — — Details →
8.11.0 26 Feb 2025 none — — Details →
8.10.2 25 Feb 2025 none — — Details →
8.10.1 14 Feb 2025 none — — Details →
8.10.0 05 Feb 2025 none — — Details →
8.9.7 04 Feb 2025 none — — Details →
8.9.6 31 Jan 2025 none — — Details →
7.8.6 20 Jan 2025 none — — Details →
6.13.8 20 Jan 2025 H1 M1 — Yes Details →
7.8.5 20 Jan 2025 none — — Details →
6.13.7 20 Jan 2025 H1 M1 — Yes Details →
8.9.5 13 Jan 2025 none — — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2019 1
  • 2020 1
  • 2022 3
  • 2023 1
  • 2024 1
  • 2025 1
  • 2026 2

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

03 Vulnerabilities

Recorded vulnerabilities for mongoose

The 5 most severe of 10 vulnerabilities recorded for this package

Search all 10 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2023-3696: Mongoose Prototype Pollution vulnerability 10.0 critical 7.3.3 17 Jul 2023
CVE-2022-24304: Mongoose Vulnerable to Prototype Pollution in Schema Object 9.8 critical 6.4.6 27 Aug 2022
CVE-2024-53900: Mongoose Search Injection Vulnerability 9.8 high 8.8.3 02 Dec 2024
CVE-2019-17426: Improper Input Validation in Automattic Mongoose 9.1 critical 5.7.5 22 Oct 2019
CVE-2025-23061: Mongoose Search Injection Vulnerability 9.0 critical 8.9.5 15 Jan 2025

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 mongoose

Is mongoose safe to use?

Vulert records 10 vulnerabilities for mongoose in npm: 4 critical, 4 high, 2 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 mongoose's Vulert package health score?

Vulert scores mongoose 80/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 mongoose affected?

No. 9.11.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.

How many vulnerabilities does mongoose have?

10 vulnerabilities are recorded for mongoose in the npm ecosystem: 4 critical, 4 high, 2 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 mongoose vulnerabilities disclosed?

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

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