Vulnerability Database · npm · Package report

mongodb: vulnerability history, versions and safety

mongodb is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 0 release, first recorded in Sep 2020. 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 H1
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.

Vulert verdict on mongodb 7.7.0 i

Updated on 23 Oct 2026

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

Package health score 89/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

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

  • Current release 7.7.0 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 03 Sep 2020 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 4,001 packages i
  • Stars 10,167 i
  • OpenSSF scorecard 5/10 i
  • Last release this month i
  • Licence Apache-2.0 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 mongodb, 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
7.7.0-dev.20261023.sha.ef6f6f3a 23 Oct 2026 none Apache-2.0 — Details →
7.7.0-dev.20261022.sha.ef6f6f3a 22 Oct 2026 none Apache-2.0 — Details →
7.7.0-dev.20261021.sha.ef6f6f3a 21 Oct 2026 none Apache-2.0 — Details →
7.7.0-dev.20261020.sha.ef6f6f3a 20 Oct 2026 none Apache-2.0 — Details →
7.7.0-dev.20261019.sha.ef6f6f3a 19 Oct 2026 none Apache-2.0 — Details →
7.7.0-dev.20261018.sha.ef6f6f3a 18 Oct 2026 none Apache-2.0 — Details →
7.7.0-dev.20261017.sha.ef6f6f3a 17 Oct 2026 none Apache-2.0 — Details →
7.7.0-dev.20261016.sha.ef6f6f3a 16 Oct 2026 none Apache-2.0 — Details →
7.7.0-dev.20261015.sha.16136bb3 15 Oct 2026 none Apache-2.0 — Details →
7.7.0-dev.20261014.sha.16136bb3 14 Oct 2026 none Apache-2.0 — Details →
7.7.0-dev.20261013.sha.16136bb3 13 Oct 2026 none Apache-2.0 — Details →
7.7.0-dev.20261012.sha.16136bb3 12 Oct 2026 none Apache-2.0 — Details →
7.7.0-dev.20261011.sha.16136bb3 11 Oct 2026 none Apache-2.0 — Details →
7.7.0-dev.20261010.sha.16136bb3 10 Oct 2026 none Apache-2.0 — Details →
7.7.0-dev.20261009.sha.a44b98b1 09 Oct 2026 none Apache-2.0 — Details →
7.7.0-dev.20261008.sha.ca0e451a 08 Oct 2026 none Apache-2.0 — Details →
7.7.0-dev.20261007.sha.df513cfa 07 Oct 2026 none Apache-2.0 — Details →
7.7.0-dev.20261006.sha.df513cfa 06 Oct 2026 none Apache-2.0 — Details →
7.7.0-dev.20261005.sha.df513cfa 05 Oct 2026 none Apache-2.0 — Details →
7.7.0-dev.20261004.sha.df513cfa 04 Oct 2026 none Apache-2.0 — Details →
7.7.0-dev.20261003.sha.df513cfa 03 Oct 2026 none Apache-2.0 — Details →
7.7.0-dev.20261002.sha.ea32fa03 02 Oct 2026 none Apache-2.0 — Details →
7.7.0-dev.20261001.sha.ea32fa03 01 Oct 2026 none Apache-2.0 — Details →
7.7.0-dev.20260930.sha.ea32fa03 30 Sep 2026 none Apache-2.0 — Details →
7.7.0-dev.20260929.sha.20b001b6 29 Sep 2026 none Apache-2.0 — Details →
7.7.0 28 Sep 2026 none Apache-2.0 — Details →
7.6.0-dev.20260928.sha.7e953ed5 28 Sep 2026 none Apache-2.0 — Details →
7.6.0-dev.20260927.sha.7e953ed5 27 Sep 2026 none Apache-2.0 — Details →
7.6.0-dev.20260926.sha.7e953ed5 26 Sep 2026 none Apache-2.0 — Details →
7.6.0-dev.20260925.sha.7e953ed5 25 Sep 2026 none Apache-2.0 — Details →
7.6.0-dev.20260924.sha.7e953ed5 24 Sep 2026 none Apache-2.0 — Details →
7.6.0-dev.20260923.sha.7e953ed5 23 Sep 2026 none Apache-2.0 — Details →
7.6.0-dev.20260922.sha.7e953ed5 22 Sep 2026 none Apache-2.0 — Details →
7.6.0-dev.20260921.sha.7e953ed5 21 Sep 2026 none Apache-2.0 — Details →
7.6.0-dev.20260920.sha.7e953ed5 20 Sep 2026 none Apache-2.0 — Details →
7.6.0-dev.20260919.sha.7e953ed5 19 Sep 2026 none Apache-2.0 — Details →
7.6.0-dev.20260918.sha.cca92501 18 Sep 2026 none Apache-2.0 — Details →
7.6.0-dev.20260917.sha.783d4892 17 Sep 2026 none Apache-2.0 — Details →
7.6.0-dev.20260916.sha.783d4892 16 Sep 2026 none Apache-2.0 — Details →
7.6.0-dev.20260915.sha.783d4892 15 Sep 2026 none Apache-2.0 — Details →
7.6.0-dev.20260914.sha.783d4892 14 Sep 2026 none Apache-2.0 — Details →
7.6.0-dev.20260913.sha.783d4892 13 Sep 2026 none Apache-2.0 — Details →
7.6.0-dev.20260912.sha.783d4892 12 Sep 2026 none Apache-2.0 — Details →
7.6.0-dev.20260911.sha.783d4892 11 Sep 2026 none Apache-2.0 — Details →
7.6.0-dev.20260910.sha.783d4892 10 Sep 2026 none Apache-2.0 — Details →
7.6.0-dev.20260909.sha.83668e62 09 Sep 2026 none Apache-2.0 — Details →
7.6.0-dev.20260908.sha.83668e62 08 Sep 2026 none Apache-2.0 — Details →
7.6.0-dev.20260907.sha.28e455de 07 Sep 2026 none Apache-2.0 — Details →
7.6.0-dev.20260906.sha.28e455de 06 Sep 2026 none Apache-2.0 — Details →
7.6.0-dev.20260905.sha.28e455de 05 Sep 2026 none Apache-2.0 — Details →
7.6.0-dev.20260904.sha.dba1544a 04 Sep 2026 none Apache-2.0 — Details →
7.6.0-dev.20260903.sha.995edbf6 03 Sep 2026 none Apache-2.0 — Details →
7.6.0-dev.20260902.sha.995edbf6 02 Sep 2026 none Apache-2.0 — Details →
7.6.0-dev.20260901.sha.995edbf6 01 Sep 2026 none Apache-2.0 — Details →
7.6.0-dev.20260831.sha.995edbf6 31 Aug 2026 none Apache-2.0 — Details →
7.6.0-dev.20260830.sha.995edbf6 30 Aug 2026 none Apache-2.0 — Details →
7.6.0-dev.20260829.sha.995edbf6 29 Aug 2026 none Apache-2.0 — Details →
7.6.0-dev.20260828.sha.d0c57c03 28 Aug 2026 none Apache-2.0 — Details →
7.6.0-dev.20260827.sha.d0c57c03 27 Aug 2026 none Apache-2.0 — Details →
7.6.0-dev.20260826.sha.b71469b3 26 Aug 2026 none Apache-2.0 — Details →
7.6.0-dev.20260825.sha.0fb2c132 25 Aug 2026 none Apache-2.0 — Details →
7.6.0 24 Aug 2026 none Apache-2.0 — Details →
7.5.0-dev.20260824.sha.bb35ded1 24 Aug 2026 none Apache-2.0 — Details →
7.5.0-dev.20260823.sha.bb35ded1 23 Aug 2026 none Apache-2.0 — Details →
7.5.0-dev.20260822.sha.bb35ded1 22 Aug 2026 none Apache-2.0 — Details →
7.5.0-dev.20260821.sha.560837b9 21 Aug 2026 none Apache-2.0 — Details →
7.5.0-dev.20260820.sha.560837b9 20 Aug 2026 none Apache-2.0 — Details →
7.5.0-dev.20260819.sha.ce33c590 19 Aug 2026 none Apache-2.0 — Details →
7.5.0-dev.20260818.sha.ce33c590 18 Aug 2026 none Apache-2.0 — Details →
7.5.0-dev.20260817.sha.ce33c590 17 Aug 2026 none Apache-2.0 — Details →
7.5.0-dev.20260816.sha.ce33c590 16 Aug 2026 none Apache-2.0 — Details →
7.5.0-dev.20260815.sha.ce33c590 15 Aug 2026 none Apache-2.0 — Details →
7.5.0-dev.20260814.sha.bc92c297 14 Aug 2026 none Apache-2.0 — Details →
7.5.0-dev.20260813.sha.dce7939f 13 Aug 2026 none Apache-2.0 — Details →
7.5.0-dev.20260812.sha.dce7939f 12 Aug 2026 none Apache-2.0 — Details →
7.5.0-dev.20260811.sha.dce7939f 11 Aug 2026 none Apache-2.0 — Details →
7.5.0-dev.20260810.sha.7f8edf30 10 Aug 2026 none Apache-2.0 — Details →
7.5.0-dev.20260809.sha.7f8edf30 09 Aug 2026 none Apache-2.0 — Details →
7.5.0-dev.20260808.sha.7f8edf30 08 Aug 2026 none Apache-2.0 — Details →
7.5.0-dev.20260807.sha.7f8edf30 07 Aug 2026 none Apache-2.0 — Details →
7.5.0-dev.20260806.sha.7f8edf30 06 Aug 2026 none Apache-2.0 — Details →
7.5.0-dev.20260805.sha.3366c21a 05 Aug 2026 none Apache-2.0 — Details →
7.5.0-dev.20260804.sha.3366c21a 04 Aug 2026 none Apache-2.0 — Details →
7.5.0-dev.20260803.sha.3d97028b 03 Aug 2026 none Apache-2.0 — Details →
7.5.0-dev.20260802.sha.3d97028b 02 Aug 2026 none Apache-2.0 — Details →
7.5.0-dev.20260801.sha.3d97028b 01 Aug 2026 none Apache-2.0 — Details →
7.5.0-dev.20260731.sha.3d97028b 31 Jul 2026 none Apache-2.0 — Details →
7.5.0-dev.20260730.sha.3d97028b 30 Jul 2026 none Apache-2.0 — Details →
7.5.0-dev.20260729.sha.e34c6475 29 Jul 2026 none Apache-2.0 — Details →
7.5.0-dev.20260728.sha.e34c6475 28 Jul 2026 none Apache-2.0 — Details →
7.5.0-dev.20260727.sha.6bff5028 27 Jul 2026 none Apache-2.0 — Details →
7.5.0-dev.20260726.sha.6bff5028 26 Jul 2026 none Apache-2.0 — Details →
7.5.0-dev.20260725.sha.6bff5028 25 Jul 2026 none Apache-2.0 — Details →
7.5.0-dev.20260724.sha.16f6fb32 24 Jul 2026 none Apache-2.0 — Details →
7.5.0-dev.20260723.sha.05460baf 23 Jul 2026 none Apache-2.0 — Details →
7.5.0-dev.20260722.sha.2d5d237e 22 Jul 2026 none Apache-2.0 — Details →
7.5.0-dev.20260721.sha.2d5d237e 21 Jul 2026 none Apache-2.0 — Details →
7.5.0-dev.20260719.sha.2d5d237e 19 Jul 2026 none Apache-2.0 — Details →
7.5.0-dev.20260718.sha.2d5d237e 18 Jul 2026 none Apache-2.0 — Details →
7.5.0-dev.20260717.sha.2d5d237e 17 Jul 2026 none Apache-2.0 — Details →
7.5.0-dev.20260716.sha.2d5d237e 16 Jul 2026 none — — Details →
7.5.0-dev.20260715.sha.dfb6b19b 15 Jul 2026 none — — Details →
7.5.0-dev.20260714.sha.52f5e61c 14 Jul 2026 none — — Details →
7.5.0-dev.20260713.sha.52f5e61c 13 Jul 2026 none — — Details →
7.5.0-dev.20260712.sha.52f5e61c 12 Jul 2026 none — — Details →
7.5.0-dev.20260711.sha.52f5e61c 11 Jul 2026 none — — Details →
7.5.0-dev.20260708.sha.cda37486 08 Jul 2026 none — — Details →
7.5.0 07 Jul 2026 none — — Details →
7.4.0-dev.20260707.sha.72c02969 07 Jul 2026 none — — Details →
7.4.0-dev.20260703.sha.b6c60daa 03 Jul 2026 none — — Details →
7.4.0-dev.20260627.sha.371579d4 27 Jun 2026 none — — Details →
7.4.0-dev.20260626.sha.53e73a90 26 Jun 2026 none — — Details →
7.4.0 25 Jun 2026 none — — Details →
7.3.0-dev.20260625.sha.88ec1595 25 Jun 2026 none — — Details →
7.3.0-dev.20260624.sha.1f5ac375 24 Jun 2026 none — — Details →
7.3.0-dev.20260623.sha.b17288ce 23 Jun 2026 none — — Details →
7.3.0-dev.20260616.sha.5b401aaf 16 Jun 2026 none — — Details →
7.3.0-dev.20260613.sha.3ba2dd2f 13 Jun 2026 none — — Details →
7.3.0-dev.20260610.sha.0a434d33 10 Jun 2026 none — — Details →
7.3.0 09 Jun 2026 none — — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 1

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

03 Vulnerabilities

Recorded vulnerabilities for mongodb

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →

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 mongodb

Is mongodb safe to use?

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

Vulert scores mongodb 89/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 mongodb affected?

No. 7.7.0, 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 mongodb should I use?

7.7.0 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 mongodb have?

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

0 vulnerabilities were recorded for mongodb in the last 12 months, and the oldest entry in this database dates to 03 Sep 2020. 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 mongodb 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 mongodb for upcoming vulnerabilities?

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