VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

pymongo: vulnerability history, versions and safety

pymongo is a package in the PyPI ecosystem. Vulert records 14 vulnerabilities for it across 120 releases, from Aug 2013 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
14 vulnerabilities recorded H2 M6 U6
i
1 with no fix published

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

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

Most recent disclosure 15 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all pymongo vulnerabilities

Vulert verdict on pymongo 4.19.0 i

Updated on 23 Oct 2026

Careful: 4.19.0 has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

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

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 4.19.0 — affected i
  • Vulnerabilities on record 14 over 13 years · 10 in the last year i
  • Latest disclosure 15 Oct 2026 i
  • Highest CVSS 8.4 i
  • With no published fix 1 i
  • Depended on by 4,206 packages i
  • Stars 4,361 i
  • OpenSSF scorecard 6/10 i
  • Last release this month i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by PyPI, refreshed 22 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 pymongo, 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
4.19.0 14 Oct 2026 M1 Apache-2.0 No Details →
4.18.3 08 Oct 2026 M1 Apache-2.0 No Details →
4.18.2 24 Sep 2026 M1 Apache-2.0 No Details →
4.18.1 10 Sep 2026 H2 M1 U3 Apache-2.0 Yes Details →
4.18.0 03 Sep 2026 H2 M3 U4 Apache-2.0 No Details →
4.17.0 20 Apr 2026 H2 M3 U4 Apache-2.0 No Details →
4.16.0 07 Jan 2026 H2 M3 U4 Apache-2.0 No Details →
4.16.0.dev0 11 Dec 2025 H2 M3 U4 Apache-2.0 No Details →
4.15.5 02 Dec 2025 H2 M3 U4 non-standard No Details →
4.15.4 11 Nov 2025 H2 M3 U4 non-standard No Details →
4.15.3 07 Oct 2025 H2 M3 U4 non-standard No Details →
4.15.2 01 Oct 2025 H2 M3 U4 non-standard No Details →
4.15.1 16 Sep 2025 H2 M3 U4 non-standard No Details →
4.15.0 10 Sep 2025 H2 M3 U4 non-standard No Details →
4.14.1 19 Aug 2025 H2 M3 U4 non-standard No Details →
4.14.0 06 Aug 2025 H2 M3 U4 non-standard No Details →
4.13.2 16 Jun 2025 H2 M3 U4 non-standard No Details →
4.13.1 11 Jun 2025 H2 M3 U4 non-standard No Details →
4.13.0 14 May 2025 H2 M3 U4 non-standard No Details →
4.13.0.dev0 14 May 2025 H2 M3 U4 non-standard No Details →
4.12.1 29 Apr 2025 H2 M3 U4 non-standard No Details →
4.12.0 08 Apr 2025 H2 M3 U4 non-standard No Details →
4.11.3 18 Mar 2025 H2 M3 U4 non-standard No Details →
4.11.2 03 Mar 2025 H2 M3 U4 non-standard No Details →
4.11.1 10 Feb 2025 H2 M3 U4 non-standard No Details →
4.11.0 28 Jan 2025 H2 M3 U4 non-standard No Details →
4.9.2 02 Oct 2024 H2 M3 U4 non-standard No Details →
4.10.1 01 Oct 2024 H2 M3 U4 non-standard No Details →
4.10.0 01 Oct 2024 H2 M3 U4 non-standard No Details →
4.9.1 18 Sep 2024 H2 M3 U4 non-standard No Details →
4.9.0 18 Sep 2024 H2 M3 U4 non-standard No Details →
4.8.0 26 Jun 2024 H2 M3 U4 non-standard No Details →
4.8.0b0 25 Jun 2024 H2 M3 U4 non-standard No Details →
4.7.3 04 Jun 2024 H2 M3 U4 non-standard No Details →
4.7.2 07 May 2024 H2 M3 U4 non-standard No Details →
4.7.1 30 Apr 2024 H2 M3 U4 non-standard No Details →
4.7.0 24 Apr 2024 H2 M3 U4 non-standard No Details →
4.6.3 28 Mar 2024 H2 M3 U4 non-standard No Details →
4.6.2 21 Feb 2024 H2 M5 U5 non-standard No Details →
4.6.1 29 Nov 2023 H2 M5 U5 non-standard No Details →
4.6.0 01 Nov 2023 H2 M5 U5 non-standard No Details →
4.5.0 22 Aug 2023 H2 M5 U5 non-standard No Details →
4.4.1 13 Jul 2023 H2 M5 U5 Apache-2.0 No Details →
4.4.0 21 Jun 2023 H2 M5 U5 non-standard No Details →
4.4.0b0 25 Jan 2023 H2 M5 U5 Apache-2.0 No Details →
4.3.3 17 Nov 2022 H2 M5 U5 Apache-2.0 No Details →
3.13.0 01 Nov 2022 H2 M5 U5 Apache-2.0 No Details →
4.3.2 18 Oct 2022 H2 M5 U5 Apache-2.0 No Details →
4.2.0 20 Jul 2022 H2 M5 U5 Apache-2.0 No Details →
4.1.1 13 Apr 2022 H2 M5 U5 Apache-2.0 No Details →
4.1.0 04 Apr 2022 H2 M5 U5 Apache-2.0 No Details →
4.0.2 03 Mar 2022 H2 M5 U5 Apache-2.0 No Details →
4.0.1 07 Dec 2021 H2 M5 U5 Apache-2.0 No Details →
3.12.3 07 Dec 2021 H2 M5 U5 Apache-2.0 No Details →
4.0.0 29 Nov 2021 H2 M5 U5 Apache-2.0 No Details →
3.12.2 29 Nov 2021 H2 M5 U5 Apache-2.0 No Details →
3.12.1 19 Oct 2021 H2 M5 U5 Apache-2.0 No Details →
3.12.0 14 Jul 2021 H2 M5 U5 Apache-2.0 No Details →
3.11.4 04 May 2021 H2 M5 U5 Apache-2.0 No Details →
3.11.3 03 Feb 2021 H2 M5 U5 Apache-2.0 No Details →
3.11.2 02 Dec 2020 H2 M5 U5 Apache-2.0 No Details →
3.11.1 17 Nov 2020 H2 M5 U5 Apache-2.0 No Details →
3.11.0 30 Jul 2020 H2 M5 U5 Apache-2.0 No Details →
3.10.1 08 Jan 2020 H2 M5 U5 Apache-2.0 No Details →
3.10.0 11 Dec 2019 H2 M5 U5 Apache-2.0 No Details →
3.9.0 14 Aug 2019 H2 M5 U5 Apache-2.0 No Details →
3.8.0 22 Apr 2019 H2 M4 U4 Apache-2.0 No Details →
3.7.2 10 Oct 2018 H2 M4 U4 Apache-2.0 No Details →
3.7.1 17 Jul 2018 H2 M4 U4 Apache-2.0 No Details →
3.7.0 26 Jun 2018 H2 M4 U4 Apache-2.0 No Details →
3.6.1 01 Mar 2018 H2 M4 U4 Apache-2.0 No Details →
3.6.0 05 Dec 2017 H2 M4 U4 Apache-2.0 No Details →
3.5.1 23 Aug 2017 H2 M4 U4 Apache-2.0 No Details →
3.5.0 08 Aug 2017 H2 M4 U4 Apache-2.0 No Details →
2.9.5 30 Jun 2017 H1 M4 U3 Apache-2.0 No Details →
3.4.0 29 Nov 2016 H1 M4 U3 Apache-2.0 No Details →
3.3.1 27 Oct 2016 H1 M4 U3 Apache-2.0 No Details →
2.9.4 30 Sep 2016 H1 M4 U3 Apache-2.0 No Details →
3.3.0 12 Jul 2016 H1 M4 U3 Apache-2.0 No Details →
3.2.2 15 Mar 2016 H1 M4 U3 Apache-2.0 No Details →
2.9.3 15 Mar 2016 H1 M4 U3 Apache-2.0 No Details →
3.2.1 02 Feb 2016 H1 M4 U3 Apache-2.0 No Details →
2.9.2 01 Feb 2016 H1 M4 U3 Apache-2.0 No Details →
3.2.0 08 Dec 2015 H1 M4 U3 Apache-2.0 No Details →
3.1.1 18 Nov 2015 H1 M4 U3 Apache-2.0 No Details →
2.9.1 17 Nov 2015 H1 M4 U3 Apache-2.0 No Details →
3.1.0 02 Nov 2015 H1 M4 U3 Apache-2.0 No Details →
2.9.0 30 Sep 2015 H1 M4 U3 Apache-2.0 No Details →
3.0.3 01 Jul 2015 H1 M4 U3 Apache-2.0 No Details →
3.0.2 12 May 2015 H1 M4 U3 Apache-2.0 No Details →
2.8.1 11 May 2015 H1 M4 U3 Apache-2.0 No Details →
3.0.1 21 Apr 2015 H1 M4 U3 Apache-2.0 No Details →
3.0.0 07 Apr 2015 H1 M4 U3 Apache-2.0 No Details →
2.8.0 28 Jan 2015 H1 M4 U3 Apache-2.0 No Details →
2.7.2 29 Jul 2014 H1 M4 U3 Apache-2.0 No Details →
2.7.1 23 May 2014 H1 M4 U3 Apache-2.0 No Details →
2.7.0 03 Apr 2014 H1 M4 U3 Apache-2.0 No Details →
2.6.3 11 Oct 2013 H1 M4 U3 Apache-2.0 No Details →
2.6.2 06 Sep 2013 H1 M4 U3 Apache-2.0 No Details →
2.6.1 04 Sep 2013 H1 M4 U3 Apache-2.0 No Details →
2.6.0 19 Aug 2013 H1 M4 U3 — No Details →
2.5.2 01 Jun 2013 H1 M4 U3 — No Details →
2.5.1 13 May 2013 H1 M5 U4 — No Details →
2.5.0 22 Mar 2013 H1 M5 U3 — No Details →
2.4.2 24 Jan 2013 H1 M5 U4 — No Details →
2.4.1 06 Dec 2012 H1 M5 U4 — No Details →
2.4.0 27 Nov 2012 H1 M5 U3 — No Details →
2.3.0 29 Aug 2012 H1 M5 U3 — No Details →
2.2.1 06 Jul 2012 H1 M5 U4 — No Details →
2.2.0 30 Apr 2012 H1 M5 U3 — No Details →
2.1.1 05 Jan 2012 H1 M5 U4 — No Details →
2.1.0 07 Dec 2011 H1 M5 U3 — No Details →
2.0.1 16 Aug 2011 H1 M5 U4 — No Details →
2.0.0 06 Aug 2011 H1 M5 U3 — No Details →
1.11.0 06 May 2011 H1 M5 U3 — No Details →
1.10.1 07 Apr 2011 H1 M5 U4 — No Details →
1.10.0 30 Mar 2011 H1 M5 U3 — No Details →
1.9.0 28 Sep 2010 H1 M5 U3 — No Details →
1.8.1 13 Aug 2010 H1 M5 U4 — No Details →
1.8.0 05 Aug 2010 H1 M5 U3 — No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2013 1
  • 2022 1
  • 2024 2
  • 2026 10

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

03 Vulnerabilities

Recorded vulnerabilities for pymongo

The 5 most severe of 14 vulnerabilities recorded for this package

Search all 14 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-96749: PyMongo Heap Out-of-Bounds Write via Signed Size Overflow in BSON Document Encoding 8.4 high 4.18.2 15 Oct 2026
CVE-2026-96749: PyMongo Heap Out-of-Bounds Write via Signed Size Overflow in BSON Document Encoding 8.4 high 4.18.2 05 Oct 2026
Improper File Identifier Handling in pymongo: PYTHON-5994 8.3 medium No fix published 10 Sep 2026
CVE-2013-2132: Null Pointer Dereference in Pymongo 6.9 medium 2.5.2 14 May 2022
CVE-2026-96748: PyMongo Host Injection Vulnerability via Percent-Encoding 6.5 high 4.18.2 05 Oct 2026

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 pymongo

Is pymongo safe to use?

Vulert records 14 vulnerabilities for pymongo in PyPI: 0 critical, 2 high, 6 medium and 0 low, plus 6 not yet rated. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is pymongo's Vulert package health score?

Vulert scores pymongo 60/100, which reads as usable, but worth attention. 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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of pymongo affected?

Yes. 4.19.0, the version you would install today, has 1 known vulnerability, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of pymongo should I use?

4.19.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 pymongo have?

14 vulnerabilities are recorded for pymongo in the PyPI ecosystem: 0 critical, 2 high, 6 medium and 0 low, plus 6 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new pymongo vulnerabilities disclosed?

10 vulnerabilities were recorded for pymongo in the last 12 months, and the oldest entry in this database dates to 15 Aug 2013. 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 pymongo 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 pymongo for upcoming vulnerabilities?

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