VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

mongosh: vulnerability history, versions and safety

mongosh is a package in the npm ecosystem. Vulert records 4 vulnerabilities for it across 96 releases, first recorded in Feb 2025. 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 H2 M1 L1
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 mongosh vulnerabilities

Vulert verdict on mongosh 2.13.0 i

Updated on 23 Oct 2026

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

Package health score 71/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Quiet

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

  • Current release 2.13.0 — unaffected i
  • Vulnerabilities on record 4 over 1 year · 0 in the last year i
  • Latest disclosure 27 Feb 2025 i
  • Highest CVSS 7.6 i
  • With no published fix 0 i
  • Stars 402 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 mongosh, 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
2.13.0 05 Oct 2026 none Apache-2.0 — Details →
2.12.0 18 Sep 2026 none Apache-2.0 — Details →
2.11.1 15 Sep 2026 none Apache-2.0 — Details →
2.10.0 13 Aug 2026 none Apache-2.0 — Details →
2.9.2 01 Jul 2026 none Apache-2.0 — Details →
2.9.1 29 Jun 2026 none Apache-2.0 — Details →
2.8.3 01 May 2026 none Apache-2.0 — Details →
2.8.2 26 Mar 2026 none Apache-2.0 — Details →
2.8.1 17 Mar 2026 none Apache-2.0 — Details →
2.7.0 12 Feb 2026 none Apache-2.0 — Details →
2.6.0 13 Jan 2026 none Apache-2.0 — Details →
2.5.10 28 Nov 2025 none Apache-2.0 — Details →
2.5.9 30 Oct 2025 none Apache-2.0 — Details →
2.5.8 09 Sep 2025 none Apache-2.0 — Details →
2.5.7 28 Aug 2025 none Apache-2.0 — Details →
2.5.6 18 Jul 2025 none Apache-2.0 — Details →
2.5.5 03 Jul 2025 none Apache-2.0 — Details →
2.5.3 18 Jun 2025 none Apache-2.0 — Details →
2.5.2 03 Jun 2025 none Apache-2.0 — Details →
2.5.1 07 May 2025 none Apache-2.0 — Details →
2.5.0 08 Apr 2025 none Apache-2.0 — Details →
2.4.2 06 Mar 2025 none Apache-2.0 — Details →
2.4.0 20 Feb 2025 none Apache-2.0 — Details →
2.3.9 05 Feb 2025 none Apache-2.0 — Details →
2.3.8 06 Jan 2025 H1 M1 L1 Apache-2.0 Yes Details →
2.3.7 17 Dec 2024 H1 M1 L1 Apache-2.0 Yes Details →
2.3.6 13 Dec 2024 H1 M1 L1 Apache-2.0 Yes Details →
2.3.5 12 Dec 2024 H1 M1 L1 Apache-2.0 Yes Details →
2.3.4 27 Nov 2024 H1 M1 L1 Apache-2.0 Yes Details →
2.3.3 30 Oct 2024 H1 M1 L1 Apache-2.0 Yes Details →
2.3.2 08 Oct 2024 H1 M1 L1 Apache-2.0 Yes Details →
2.3.1 05 Sep 2024 H1 M1 L1 Apache-2.0 Yes Details →
2.3.0 16 Aug 2024 H1 M1 L1 Apache-2.0 Yes Details →
2.2.15 30 Jul 2024 H2 M1 L1 Apache-2.0 Yes Details →
2.2.12 11 Jul 2024 H2 M1 L1 Apache-2.0 Yes Details →
2.2.11 09 Jul 2024 H2 M1 L1 Apache-2.0 Yes Details →
2.2.10 24 Jun 2024 H2 M1 L1 Apache-2.0 Yes Details →
2.2.9 14 Jun 2024 H2 M1 L1 Apache-2.0 Yes Details →
2.2.6 17 May 2024 H2 M1 L1 Apache-2.0 Yes Details →
2.2.5 24 Apr 2024 H2 M1 L1 Apache-2.0 Yes Details →
2.2.4 15 Apr 2024 H2 M1 L1 Apache-2.0 Yes Details →
2.2.3 04 Apr 2024 H2 M1 L1 Apache-2.0 Yes Details →
2.2.2 26 Mar 2024 H2 M1 L1 Apache-2.0 Yes Details →
2.2.1 19 Mar 2024 H2 M1 L1 Apache-2.0 Yes Details →
2.2.0 14 Mar 2024 H2 M1 L1 Apache-2.0 Yes Details →
2.1.5 19 Feb 2024 H2 M1 L1 Apache-2.0 Yes Details →
2.1.4 08 Feb 2024 H2 M1 L1 Apache-2.0 Yes Details →
2.1.3 29 Jan 2024 H2 M1 L1 Apache-2.0 Yes Details →
2.1.1 05 Dec 2023 H2 M1 L1 Apache-2.0 Yes Details →
2.1.0 21 Nov 2023 H2 M1 L1 Apache-2.0 Yes Details →
2.0.2 16 Oct 2023 H2 M1 L1 Apache-2.0 Yes Details →
2.0.1 14 Sep 2023 H2 M1 L1 Apache-2.0 Yes Details →
2.0.0 06 Sep 2023 H2 M1 L1 Apache-2.0 Yes Details →
1.10.6 25 Aug 2023 H2 M1 L1 Apache-2.0 Yes Details →
1.10.5 14 Aug 2023 H2 M1 L1 Apache-2.0 Yes Details →
1.10.4 10 Aug 2023 H2 M1 L1 Apache-2.0 Yes Details →
1.10.3 31 Jul 2023 H2 M1 L1 Apache-2.0 Yes Details →
1.10.2 28 Jul 2023 H2 M1 L1 Apache-2.0 Yes Details →
1.10.1 21 Jun 2023 H2 M1 L1 Apache-2.0 Yes Details →
1.10.0 13 Jun 2023 H2 M1 L1 Apache-2.0 Yes Details →
1.9.1 25 May 2023 H2 M1 L1 Apache-2.0 Yes Details →
1.9.0 17 May 2023 H2 M1 L1 Apache-2.0 Yes Details →
1.8.2 28 Apr 2023 H2 M1 L1 Apache-2.0 Yes Details →
1.8.1 24 Apr 2023 H2 M1 L1 Apache-2.0 Yes Details →
1.8.0 28 Feb 2023 H2 M1 L1 Apache-2.0 Yes Details →
1.7.1 13 Feb 2023 H2 M1 L1 Apache-2.0 Yes Details →
1.7.0 10 Feb 2023 H2 M1 L1 Apache-2.0 Yes Details →
1.6.2 09 Jan 2023 H2 M1 L1 Apache-2.0 Yes Details →
1.6.1 01 Dec 2022 H2 M1 L1 Apache-2.0 Yes Details →
1.6.0 20 Sep 2022 H2 M1 L1 Apache-2.0 Yes Details →
1.5.4 31 Jul 2022 H2 M1 L1 Apache-2.0 Yes Details →
1.5.3 29 Jul 2022 H2 M1 L1 Apache-2.0 Yes Details →
1.5.2 27 Jul 2022 H2 M1 L1 Apache-2.0 Yes Details →
1.5.1 14 Jul 2022 H2 M1 L1 Apache-2.0 Yes Details →
1.5.0 02 Jun 2022 H2 M1 L1 Apache-2.0 Yes Details →
1.4.2 17 May 2022 H2 M1 L1 Apache-2.0 Yes Details →
1.4.1 12 May 2022 H2 M1 L1 Apache-2.0 Yes Details →
1.3.1 21 Mar 2022 H2 M1 L1 Apache-2.0 Yes Details →
1.3.0 17 Mar 2022 H2 M1 L1 Apache-2.0 Yes Details →
1.2.3 09 Mar 2022 H2 M1 L1 Apache-2.0 Yes Details →
1.2.2 25 Feb 2022 H2 M1 L1 Apache-2.0 Yes Details →
1.2.1 23 Feb 2022 H2 M1 L1 Apache-2.0 Yes Details →
1.1.9 18 Jan 2022 H2 M1 L1 Apache-2.0 Yes Details →
1.1.8 11 Jan 2022 H2 M1 L1 Apache-2.0 Yes Details →
1.1.7 14 Dec 2021 H2 M1 L1 Apache-2.0 Yes Details →
1.1.6 02 Dec 2021 H2 M1 L1 Apache-2.0 Yes Details →
1.1.5 01 Dec 2021 H2 M1 L1 Apache-2.0 Yes Details →
1.1.4 24 Nov 2021 H2 M1 L1 Apache-2.0 Yes Details →
1.1.2 05 Nov 2021 H2 M1 L1 Apache-2.0 Yes Details →
1.1.1 28 Oct 2021 H2 M1 L1 Apache-2.0 Yes Details →
1.1.0 07 Oct 2021 H2 M1 L1 Apache-2.0 Yes Details →
1.0.7 22 Sep 2021 H2 M1 L1 Apache-2.0 Yes Details →
1.0.6 14 Sep 2021 H2 M1 L1 Apache-2.0 Yes Details →
1.0.5 12 Aug 2021 H2 M1 L1 Apache-2.0 Yes Details →
1.0.4 04 Aug 2021 H2 M1 L1 Apache-2.0 Yes Details →
1.0.3 29 Jul 2021 H2 M1 L1 Apache-2.0 Yes Details →
1.0.1 21 Jul 2021 H2 M1 L1 Apache-2.0 Yes Details →
0.15.6 09 Jul 2021 H2 M1 L1 Apache-2.0 Yes Details →
0.15.5 02 Jul 2021 H2 M1 L1 Apache-2.0 Yes Details →
0.15.4 01 Jul 2021 H2 M1 L1 Apache-2.0 Yes Details →
0.15.1 18 Jun 2021 H2 M1 L1 — Yes Details →
0.15.0 11 Jun 2021 H2 M1 L1 — Yes Details →
0.14.0 28 May 2021 H2 M1 L1 — Yes Details →
0.13.2 20 May 2021 H2 M1 L1 — Yes Details →
0.13.1 18 May 2021 H2 M1 L1 — Yes Details →
0.12.1 30 Apr 2021 H2 M1 L1 — Yes Details →
0.12.0 23 Apr 2021 H2 M1 L1 — Yes Details →
0.11.0 08 Apr 2021 H2 M1 L1 — Yes Details →
0.10.1 01 Apr 2021 H2 M1 L1 — Yes Details →
0.10.0 31 Mar 2021 H2 M1 L1 — Yes Details →
0.9.0 10 Mar 2021 H2 M1 L1 — Yes Details →
0.8.3 03 Mar 2021 H2 M1 L1 — Yes Details →
0.8.2 24 Feb 2021 H2 M1 L1 — Yes Details →
0.8.1 23 Feb 2021 H2 M1 L1 — Yes Details →
0.8.0 17 Feb 2021 H2 M1 L1 — Yes Details →
0.7.7 03 Feb 2021 H2 M1 L1 — Yes Details →
0.6.1 30 Nov 2020 H2 M1 L1 — Yes Details →
0.6.0 30 Nov 2020 H2 M1 L1 — Yes Details →
0.5.2 11 Nov 2020 H2 M1 L1 — Yes Details →
0.5.1 11 Nov 2020 H2 M1 L1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 4

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

03 Vulnerabilities

Recorded vulnerabilities for mongosh

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2025-1691: MongoDB Shell Control Character Injection Vulnerability 7.6 high 2.3.9 27 Feb 2025
CVE-2025-1756: mongosh Local Privilege Escalation Vulnerability 7.5 high 2.3.0 27 Feb 2025
CVE-2025-1692: MongoDB Shell Control Character Injection Vulnerability 6.3 medium 2.3.9 27 Feb 2025
CVE-2025-1693: MongoDB Shell Control Character Injection Vulnerability 3.9 low 2.3.9 27 Feb 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: 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 mongosh

Is mongosh safe to use?

Vulert records 4 vulnerabilities for mongosh in npm: 0 critical, 2 high, 1 medium and 1 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 mongosh's Vulert package health score?

Vulert scores mongosh 71/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 mongosh affected?

No. 2.13.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 mongosh should I use?

2.13.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 mongosh have?

4 vulnerabilities are recorded for mongosh in the npm ecosystem: 0 critical, 2 high, 1 medium and 1 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new mongosh vulnerabilities disclosed?

0 vulnerabilities were recorded for mongosh in the last 12 months, and the oldest entry in this database dates to 27 Feb 2025. 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 mongosh 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 mongosh for upcoming vulnerabilities?

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