Vulnerability Database · PyPI · Package report
ldap3: vulnerability history, versions and safety
ldap3 is a package in the PyPI ecosystem. Vulert holds no vulnerabilities for it yet.
Nothing recorded for this package in the PyPI ecosystem.
Every vulnerability has a patched version to move to.
No published version shipped hostile code.
Vulert verdict on ldap3 2.9.1 i
Updated on 23 Oct 2026
Good news: 2.9.1, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Unmaintained
- Popularity Widely used
- Community Quiet
What to do: Stay on 2.9.1 or newer. This can change: a vulnerability disclosed tomorrow can affect 2.9.1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release 2.9.1 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Depended on by 589 packages i
- Stars 936 i
- OpenSSF scorecard 2/10 i
- Last release 63 months ago i
- Licence LGPL-3.0-or-later i
Version list, release dates, licence and dependants published by PyPI, 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 ldap3, 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.
- 2.10.2rc4 18 Apr 2026
- 2.10.2rc3 09 Nov 2025
- 2.10.2rc2 19 Apr 2025
- 2.9.1 18 Jul 2021
- 2.9.0 24 Jan 2021
- 2.8.1 07 Sep 2020
- 2.8.0 08 Aug 2020
- 2.7.0 01 Mar 2020
- 2.6.1 06 Sep 2019
- 2.6.0 24 Mar 2019
- 2.5.2 28 Dec 2018
- 2.5.1 01 Aug 2018
- 2.5.0 14 Apr 2018
- 2.4.1 21 Jan 2018
- 2.4.0 14 Nov 2017
- 2.3.0 02 Aug 2017
- 2.2.4 07 May 2017
- 2.2.3 30 Apr 2017
- 2.2.2 17 Mar 2017
- 2.2.1 12 Feb 2017
- 2.2.0 16 Jan 2017
- 2.1.1 18 Nov 2016
- 2.1.0 03 Nov 2016
- 2.0.9 28 Oct 2016
- 0.9.8.7.post1 06 Sep 2016
- 1.4.0 18 Jul 2016
- 1.3.3 03 Jul 2016
- 1.3.1 11 May 2016
- 1.2.2 23 Mar 2016
- 1.2.1 21 Mar 2016
- 1.1.2 09 Mar 2016
- 1.0.4 25 Jan 2016
- 1.0.3 19 Dec 2015
- 1.0.2 07 Dec 2015
- 0.9.8.7.post1-py2.6
- 0.9.8.7.post1-py2.7
- 0.9.8.7.post1-py3.5
- 0.9.8.7.post1.win-amd64
- 1.0.2-py2.6
- 1.0.2-py2.7
- 1.0.2-py3.5
- 1.0.2.win-amd64
- 1.0.3-py2.6
- 1.0.3-py2.7
- 1.0.3-py3.5
- 1.0.3.win-amd64
- 1.0.4-py2.6
- 1.0.4-py2.7
- 1.0.4-py3.5
- 1.0.4.win-amd64
- 1.1.2-py2.6
- 1.1.2-py2.7
- 1.1.2-py3.5
- 1.1.2.win-amd64
- 1.2.1-py2.6
- 1.2.1-py2.7
- 1.2.1-py3.5
- 1.2.1.win-amd64
- 1.2.2-py2.6
- 1.2.2-py2.7
- 1.2.2-py3.5
- 1.2.2.win-amd64
- 1.3.1-py2.6
- 1.3.1-py2.7
- 1.3.1-py3.5
- 1.3.1.win-amd64
- 1.3.3-py2.6
- 1.3.3-py2.7
- 1.3.3-py3.5
- 1.3.3.win-amd64
- 1.4.0-py2.6
- 1.4.0-py2.7
- 1.4.0-py3.5
- 1.4.0.win-amd64
- 2.0.9-py2.6
- 2.0.9-py2.7
- 2.0.9-py3.5
- 2.0.9.win-amd64
- 2.1.0-py2.6
- 2.1.0-py2.7
- 2.1.0-py3.5
- 2.1.0.win-amd64
- 2.1.1-py2.6
- 2.1.1-py2.7
- 2.1.1-py3.5
- 2.1.1.win-amd64
- 2.2.0-py2.6
- 2.2.0-py2.7
- 2.2.0-py3.6
- 2.2.0.win-amd64
- 2.2.1-py2.6
- 2.2.1-py2.7
- 2.2.1-py3.6
- 2.2.1.win-amd64
- 2.2.2-py2.6
- 2.2.2-py2.7
- 2.2.2-py3.6
- 2.2.2.win-amd64
- 2.2.3-py2.6
- 2.2.3-py2.7
- 2.2.3-py3.6
- 2.2.3.win-amd64
- 2.2.4-py2.6
- 2.2.4-py2.7
- 2.2.4-py3.6
- 2.2.4.win-amd64
- 2.3-py2.6
- 2.3-py2.7
- 2.3-py3.6
- 2.3.win-amd64
- 2.4-py2.6
- 2.4-py2.7
- 2.4-py3.6
- 2.4.1-py2.6
- 2.4.1-py2.7
- 2.4.1-py3.6
- 2.4.1.win-amd64
- 2.4.win-amd64
- 2.5-py2.6
- 2.5-py2.7
The newest 120 of 154 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.
02 Disclosure history
How often vulnerabilities are recorded
No dated vulnerabilities are recorded for this package yet.
Other ways into the data
03 Vulnerabilities
Recorded vulnerabilities for ldap3
No vulnerabilities match this view.
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
Questions
About ldap3
Is ldap3 safe to use?
Vulert has no vulnerabilities on record for ldap3 in PyPI at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.
What is ldap3's Vulert package health score?
Vulert scores ldap3 57/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).
Is the latest version of ldap3 affected?
No. 2.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 ldap3 should I use?
2.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 ldap3 have?
0 vulnerabilities are recorded for ldap3 in the PyPI ecosystem: 0 critical, 0 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 ldap3 vulnerabilities disclosed?
0 vulnerabilities were recorded for ldap3 in the last 12 months. 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 ldap3 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 ldap3 for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the ldap3 version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.