Vulnerability Database · PyPI · gitpython · Version
gitpython 2.1.4
2.1.4 is affected by 86 vulnerabilities.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: 3.2.1.
Critical 6 High 54 Medium 10 Low 0 Unrated 16
-
Released 10 Jun 2017
Licence non-standard
Also known from other sources 68
Newer releases 116
Database updated 23/Oct/2026
Release and licence data published by PyPI. 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 Vulnerabilities affecting this version
gitpython 2.1.4 vulnerabilities
86 vulnerabilities cover gitpython 2.1.4. Scroll the table for all of them, or open the full list in the database.
Looking for another version, or everything Vulert holds for gitpython?
Questions
About gitpython 2.1.4
Is gitpython 2.1.4 vulnerable?
Yes. 86 vulnerabilities in the Vulert database cover gitpython 2.1.4: 6 critical, 54 high, 10 medium and 0 low, plus 16 not yet rated. The upgrade Vulert recommends is 3.2.1, and each entry above names the fixed version to move to.
Which version of gitpython should I use instead of 2.1.4?
3.2.1 is the version Vulert recommends for this release line. The version table on the package page lists every release with the vulnerabilities recorded against it.
Is 2.1.4 the latest release of gitpython?
No. 2.1.4 was published 10 Jun 2017, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.
How do I monitor gitpython for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the gitpython version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.