VulertSecurity VulertSecurity

Vulnerability Database · crates.io · Package report

mongodb: vulnerability history, versions and safety

mongodb is a package in the crates.io ecosystem. Vulert records 3 vulnerabilities for it across 90 releases, from May 2022 to Oct 2025. 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 H1 M2
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 mongodb vulnerabilities

Vulert verdict on mongodb 3.9.1 i

Updated on 23 Oct 2026

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

Package health score 73/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Quiet

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

  • Current release 3.9.1 — unaffected i
  • Vulnerabilities on record 3 over 3 years · 0 in the last year i
  • Latest disclosure 13 Oct 2025 i
  • Highest CVSS 8.0 i
  • With no published fix 0 i
  • Stars 1,520 i
  • OpenSSF scorecard 4/10 i
  • Last release 1 month ago i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by crates.io, 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
3.9.1 10 Sep 2026 none Apache-2.0 — Details →
3.9.0 03 Sep 2026 none Apache-2.0 — Details →
3.8.2 27 Aug 2026 none Apache-2.0 — Details →
3.8.1 21 Aug 2026 none Apache-2.0 — Details →
3.8.0 09 Jul 2026 none Apache-2.0 — Details →
3.7.0 21 May 2026 none Apache-2.0 — Details →
3.6.0 20 Apr 2026 none Apache-2.0 — Details →
3.5.2 18 Mar 2026 none Apache-2.0 — Details →
3.5.1 03 Feb 2026 none Apache-2.0 — Details →
3.5.0 14 Jan 2026 none Apache-2.0 — Details →
3.4.1 20 Nov 2025 none Apache-2.0 — Details →
3.3.0 03 Sep 2025 none Apache-2.0 — Details →
3.2.5 22 Aug 2025 none Apache-2.0 — Details →
3.2.4 30 Jun 2025 H1 Apache-2.0 Yes Details →
3.2.3 19 Mar 2025 H1 Apache-2.0 Yes Details →
3.2.2 06 Mar 2025 H1 Apache-2.0 Yes Details →
3.2.1 04 Feb 2025 H1 Apache-2.0 Yes Details →
3.2.0 16 Jan 2025 H1 Apache-2.0 Yes Details →
3.1.1 12 Dec 2024 H1 Apache-2.0 Yes Details →
3.1.0 30 Aug 2024 H1 Apache-2.0 Yes Details →
3.0.1 09 Jul 2024 H1 Apache-2.0 Yes Details →
3.0.0 25 Jun 2024 H1 Apache-2.0 Yes Details →
3.0.0-beta 07 Jun 2024 H1 Apache-2.0 Yes Details →
2.8.2 15 Mar 2024 H1 Apache-2.0 Yes Details →
2.8.1 09 Feb 2024 H1 M1 Apache-2.0 Yes Details →
2.8.0 11 Dec 2023 H1 M1 Apache-2.0 Yes Details →
2.7.1 01 Nov 2023 H1 M1 Apache-2.0 Yes Details →
2.7.0 27 Sep 2023 H1 M1 Apache-2.0 Yes Details →
2.7.0-beta.1 18 Sep 2023 H1 M1 Apache-2.0 Yes Details →
2.7.0-beta 30 Aug 2023 H1 M1 Apache-2.0 Yes Details →
2.6.1 16 Aug 2023 H1 M1 Apache-2.0 Yes Details →
2.6.0 22 Jun 2023 H1 M1 Apache-2.0 Yes Details →
2.5.0 19 Apr 2023 H1 M1 Apache-2.0 Yes Details →
2.4.0 01 Mar 2023 H1 M1 Apache-2.0 Yes Details →
2.4.0-beta.2 09 Feb 2023 H1 M1 Apache-2.0 Yes Details →
2.4.0-beta.1 31 Jan 2023 H1 M1 Apache-2.0 Yes Details →
2.4.0-beta 13 Jan 2023 H1 M1 Apache-2.0 Yes Details →
2.3.1 03 Oct 2022 H1 M1 Apache-2.0 Yes Details →
2.3.0 19 Jul 2022 H1 M1 Apache-2.0 Yes Details →
2.3.0-beta 07 Jun 2022 H1 M1 Apache-2.0 Yes Details →
2.2.2 03 Jun 2022 H1 M1 Apache-2.0 Yes Details →
2.2.1 22 Apr 2022 H1 M1 Apache-2.0 Yes Details →
2.2.0 14 Apr 2022 H1 M1 Apache-2.0 Yes Details →
2.2.0-beta 28 Mar 2022 H1 M1 Apache-2.0 Yes Details →
1.2.5 14 Dec 2021 H1 M1 Apache-2.0 Yes Details →
2.1.0 14 Dec 2021 H1 M1 Apache-2.0 Yes Details →
2.1.0-beta 16 Nov 2021 H1 M1 Apache-2.0 Yes Details →
1.2.4 12 Nov 2021 H1 M1 Apache-2.0 Yes Details →
2.0.2 12 Nov 2021 H1 M1 Apache-2.0 Yes Details →
2.0.1 12 Oct 2021 H1 M1 Apache-2.0 Yes Details →
2.0.0 07 Sep 2021 H1 M1 Apache-2.0 Yes Details →
1.2.3 25 Aug 2021 H1 M1 Apache-2.0 Yes Details →
2.0.0-beta.3 06 Aug 2021 H1 Apache-2.0 Yes Details →
2.0.0-beta.2 25 Jun 2021 H1 Apache-2.0 Yes Details →
1.2.2 09 Jun 2021 H1 M1 Apache-2.0 Yes Details →
2.0.0-beta.1 01 Jun 2021 H1 Apache-2.0 Yes Details →
2.0.0-beta 14 May 2021 H1 Apache-2.0 Yes Details →
2.0.0-alpha.1 09 Apr 2021 H1 M1 Apache-2.0 Yes Details →
1.2.1 06 Apr 2021 H1 M1 Apache-2.0 Yes Details →
1.2.0 16 Feb 2021 H1 M1 Apache-2.0 Yes Details →
2.0.0-alpha 30 Jan 2021 H1 M1 Apache-2.0 Yes Details →
1.1.1 01 Sep 2020 H1 M1 Apache-2.0 Yes Details →
1.1.0 19 Aug 2020 H1 M1 Apache-2.0 Yes Details →
1.1.0-beta 31 Jul 2020 H1 M1 Apache-2.0 Yes Details →
1.0.0 08 Jun 2020 H1 M1 Apache-2.0 Yes Details →
0.11.0 03 Jun 2020 H1 Apache-2.0 Yes Details →
0.10.0 05 May 2020 H1 Apache-2.0 Yes Details →
0.9.2 17 Mar 2020 H1 Apache-2.0 Yes Details →
0.9.1 29 Jan 2020 H1 Apache-2.0 Yes Details →
0.9.0 19 Dec 2019 H1 Apache-2.0 Yes Details →
0.9.0-alpha 19 Dec 2019 H1 Apache-2.0 Yes Details →
0.4.0 09 Sep 2019 H1 Apache-2.0 Yes Details →
0.3.12 16 Nov 2018 H1 Apache-2.0 Yes Details →
0.3.11 15 Nov 2018 H1 Apache-2.0 Yes Details →
0.3.10 20 Jul 2018 H1 Apache-2.0 Yes Details →
0.3.9 09 Jul 2018 H1 Apache-2.0 Yes Details →
0.3.8 06 Jul 2018 H1 Apache-2.0 Yes Details →
0.3.7 02 Oct 2017 H1 Apache-2.0 Yes Details →
0.3.6 30 Sep 2017 H1 Apache-2.0 Yes Details →
0.3.5 15 Sep 2017 H1 Apache-2.0 Yes Details →
0.3.4 10 Sep 2017 H1 Apache-2.0 Yes Details →
0.3.3 21 Aug 2017 H1 Apache-2.0 Yes Details →
0.3.2 30 Jul 2017 H1 Apache-2.0 Yes Details →
0.3.1 23 Jun 2017 H1 Apache-2.0 Yes Details →
0.3.0 03 Jun 2017 H1 Apache-2.0 Yes Details →
0.2.9 17 May 2017 H1 Apache-2.0 Yes Details →
0.2.8 15 May 2017 H1 Apache-2.0 Yes Details →
0.2.7 24 Apr 2017 H1 Apache-2.0 Yes Details →
0.2.6 11 Apr 2017 H1 Apache-2.0 Yes Details →
0.2.5 08 Apr 2017 H1 Apache-2.0 Yes Details →
0.2.3 04 Mar 2017 H1 Apache-2.0 Yes Details →
0.2.2 23 Feb 2017 H1 Apache-2.0 Yes Details →
0.2.1 13 Feb 2017 H1 Apache-2.0 Yes Details →
0.2.0 29 Jan 2017 H1 Apache-2.0 Yes Details →
0.1.8 14 Nov 2016 H1 Apache-2.0 Yes Details →
0.1.7 12 Oct 2016 H1 Apache-2.0 Yes Details →
0.1.6 31 Aug 2016 H1 Apache-2.0 Yes Details →
0.1.5 20 Aug 2016 H1 Apache-2.0 Yes Details →
0.1.4 28 Apr 2016 H1 Apache-2.0 Yes Details →
0.1.3 19 Jan 2016 H1 Apache-2.0 Yes Details →
0.1.1 18 Nov 2015 H1 — Yes Details →
0.1.0 13 Aug 2015 H1 — Yes Details →
0.0.1 22 May 2015 H1 — Yes Details →

All 103 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 1
  • 2024 1
  • 2025 1

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 mongodb

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2025-11695: MongoDB Rust Driver Certificate Validation Disabled 8.0 high 3.2.5 13 Oct 2025
CVE-2024-6382: MongoDB Rust Driver Unintended Command Execution Vulnerability 6.4 medium 2.8.2 02 Jul 2024
CVE-2021-20332: Exposure of Sensitive Information to an Unauthorized Actor in MongoDB Rust Driver 4.4 medium 2.0.0-beta 24 May 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 mongodb

Is mongodb safe to use?

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

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

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

Which version of mongodb should I use?

3.9.1 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?

3 vulnerabilities are recorded for mongodb in the crates.io ecosystem: 0 critical, 1 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 mongodb vulnerabilities disclosed?

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