Vulnerability Database · Packagist · Package report

mongodb/mongodb: vulnerability history, versions and safety

mongodb/mongodb is a package in the Packagist ecosystem. Vulert records 4 vulnerabilities for it across 71 releases, from Aug 2023 to Oct 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded H1 M3
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
3 in the last 12 months

Most recent disclosure 05 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on mongodb/mongodb i

Updated on 23 Oct 2026

Careful: one of the 4 vulnerabilities Vulert records for this package has no fix yet. Plan around that one, or apply its workaround. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 4 vulnerabilities on record across 3 years, 3 in the last year.

What to do: Plan around the 1 vulnerability with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 4 over 3 years · 3 in the last year i
  • Latest disclosure 05 Oct 2026 i
  • Highest CVSS 8.3 i
  • With no published fix 1 i

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 holds for mongodb/mongodb, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
2.5.0 M1 No Details →
2.4.2 M1 No Details →
2.4.1 M1 No Details →
2.4.0 M1 No Details →
2.3.0 M1 No Details →
2.2.0 M1 No Details →
2.1.2 M1 No Details →
2.1.1 M1 No Details →
2.1.0 M1 No Details →
2.0.0 M1 No Details →
1.21.5 M2 No Details →
1.21.4 M2 No Details →
1.21.3 H1 M2 No Details →
1.21.2 H1 M2 No Details →
1.21.1 H1 M2 No Details →
1.21.0 H1 M2 No Details →
1.20.0 H1 M2 No Details →
1.19.1 H1 M2 No Details →
1.19.0 H1 M2 No Details →
1.18.0 H1 M2 No Details →
1.17.1 H1 M2 No Details →
1.17.0 H1 M2 No Details →
1.16.1 H1 M2 No Details →
1.16.0 H1 M2 No Details →
1.15.0 H1 M2 No Details →
1.13.1 H1 M2 No Details →
1.13.0 H1 M2 No Details →
1.13.0-beta1 H1 M2 No Details →
1.12.0 H1 M2 No Details →
1.11.0 H1 M2 No Details →
1.10.1 H1 M2 No Details →
1.10.0 H1 M2 No Details →
1.9.0 H1 M3 No Details →
1.9.0-alpha1 H1 M3 No Details →
1.8.0 H1 M3 No Details →
1.8.0-RC1 H1 M3 No Details →
1.7.2 H1 M3 No Details →
1.7.1 H1 M3 No Details →
1.7.0 H1 M3 No Details →
1.7.0-rc1 H1 M3 No Details →
1.7.0-beta2 H1 M3 No Details →
1.7.0-beta1 H1 M3 No Details →
1.6.1 H1 M3 No Details →
1.6.0 H1 M3 No Details →
1.5.2 H1 M3 No Details →
1.5.1 H1 M3 No Details →
1.5.0 H1 M3 No Details →
1.4.3 H1 M3 No Details →
1.4.2 H1 M3 No Details →
1.4.1 H1 M3 No Details →
1.4.0 H1 M3 No Details →
1.3.2 H1 M3 No Details →
1.3.1 H1 M3 No Details →
1.3.0 H1 M3 No Details →
1.2.0 H1 M3 No Details →
1.2.0-alpha1 H1 M3 No Details →
1.1.2 H1 M3 No Details →
1.1.1 H1 M3 No Details →
1.1.0 H1 M3 No Details →
1.1.0-alpha1 H1 M1 Yes Details →
1.0.5 H1 M1 Yes Details →
1.0.4 H1 M1 Yes Details →
1.0.3 H1 M1 Yes Details →
1.0.2 H1 M1 Yes Details →
1.0.1 H1 M1 Yes Details →
1.0.0 H1 M1 Yes Details →
1.0.0-beta2 H1 Yes Details →
1.0.0-beta1 H1 Yes Details →
1.0.0-alpha1 H1 Yes Details →
0.2.0 H1 Yes Details →
0.1.0 H1 Yes Details →

Newest 71 of 71 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 1
  • 2026 3

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

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/mongodb

Is mongodb/mongodb safe to use?

Vulert records 4 vulnerabilities for mongodb/mongodb in Packagist: 0 critical, 1 high, 3 medium and 0 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

How many vulnerabilities does mongodb/mongodb have?

4 vulnerabilities are recorded for mongodb/mongodb in the Packagist ecosystem: 0 critical, 1 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 mongodb/mongodb vulnerabilities disclosed?

3 vulnerabilities were recorded for mongodb/mongodb in the last 12 months, and the oldest entry in this database dates to 29 Aug 2023. 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/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/mongodb for upcoming vulnerabilities?

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