VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

gitpython: vulnerability history, versions and safety

gitpython is a package in the PyPI ecosystem. Vulert records 91 vulnerabilities for it across 116 releases, from Dec 2022 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
91 vulnerabilities recorded C5 H42 M8 U36
i
17 with no fix published

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

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

Most recent disclosure 22 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all gitpython vulnerabilities

Vulert verdict on gitpython 3.2.1 i

Updated on 23 Oct 2026

Careful: 3.2.1 has 17 known vulnerabilities, and 17 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 50/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 3.2.1 — affected i
  • Vulnerabilities on record 91 over 3 years · 81 in the last year i
  • Latest disclosure 22 Oct 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 17 i
  • Depended on by 9,263 packages i
  • Stars 5,191 i
  • OpenSSF scorecard 6/10 i
  • Last release this month i
  • Licence BSD-3-Clause 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 gitpython, 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
3.2.1 14 Oct 2026 C2 H15 BSD-3-Clause No Details →
3.2.0 30 Sep 2026 H2 BSD-3-Clause No Details →
3.1.62 07 Sep 2026 H2 BSD-3-Clause No Details →
3.1.61 28 Aug 2026 H2 M1 BSD-3-Clause No Details →
3.1.60 25 Aug 2026 H2 M1 BSD-3-Clause No Details →
3.1.59 10 Aug 2026 H6 M2 U3 BSD-3-Clause No Details →
3.1.58 04 Aug 2026 C2 H11 M3 U8 BSD-3-Clause No Details →
3.1.57 26 Jul 2026 C2 H21 M4 U14 BSD-3-Clause No Details →
3.1.56 25 Jul 2026 C2 H22 M5 U16 BSD-3-Clause No Details →
3.1.55 23 Jul 2026 C2 H22 M6 U17 BSD-3-Clause No Details →
3.1.54 22 Jul 2026 C2 H23 M6 U18 BSD-3-Clause No Details →
3.1.53 20 Jul 2026 C2 H26 M6 U21 BSD-3-Clause No Details →
3.1.52 16 Jul 2026 C2 H27 M6 U22 BSD-3-Clause No Details →
3.1.51 12 Jul 2026 C2 H29 M6 U23 BSD-3-Clause No Details →
3.1.50 06 May 2026 C3 H34 M6 U25 BSD-3-Clause No Details →
3.1.49 29 Apr 2026 C2 H34 M6 U27 BSD-3-Clause No Details →
3.1.48 28 Apr 2026 C2 H35 M6 U28 BSD-3-Clause No Details →
3.1.47 22 Apr 2026 C2 H36 M6 U29 BSD-3-Clause No Details →
3.1.46 01 Jan 2026 C2 H38 M6 U31 BSD-3-Clause No Details →
3.1.45 24 Jul 2025 C2 H38 M6 U31 BSD-3-Clause No Details →
3.1.44 02 Jan 2025 C2 H38 M6 U31 BSD-3-Clause No Details →
3.1.43 31 Mar 2024 C2 H38 M6 U31 BSD-3-Clause No Details →
3.1.42 15 Feb 2024 C2 H38 M6 U31 BSD-3-Clause No Details →
3.1.41 10 Jan 2024 C2 H38 M6 U31 BSD-3-Clause No Details →
3.1.40 18 Oct 2023 C2 H39 M6 U32 non-standard No Details →
3.1.38 17 Oct 2023 C2 H39 M6 U32 non-standard No Details →
3.1.37 22 Sep 2023 C2 H39 M6 U32 non-standard No Details →
3.1.36 12 Sep 2023 C2 H39 M7 U32 non-standard No Details →
3.1.35 07 Sep 2023 C2 H39 M7 U32 non-standard No Details →
3.1.34 02 Sep 2023 C2 H39 M7 U33 non-standard No Details →
3.1.33 01 Sep 2023 C2 H39 M7 U33 non-standard No Details →
3.1.32 10 Jul 2023 C2 H40 M7 U34 non-standard No Details →
3.1.31 16 Feb 2023 C3 H40 M7 U35 non-standard No Details →
3.1.30 29 Dec 2022 C3 H40 M7 U35 non-standard No Details →
3.1.29 10 Oct 2022 C4 H39 M7 U35 non-standard No Details →
3.1.28 07 Oct 2022 C4 H39 M7 U35 non-standard No Details →
3.1.27 20 Feb 2022 C4 H39 M7 U35 non-standard No Details →
3.1.26 10 Jan 2022 C4 H39 M7 U35 non-standard No Details →
3.1.25 07 Jan 2022 C4 H39 M7 U35 non-standard No Details →
3.1.24 18 Sep 2021 C4 H39 M7 U35 non-standard No Details →
3.1.23 10 Sep 2021 C4 H39 M7 U35 non-standard No Details →
3.1.22 10 Sep 2021 C4 H39 M7 U35 non-standard No Details →
3.1.20 28 Jul 2021 C4 H39 M7 U35 non-standard No Details →
3.1.19 23 Jul 2021 C4 H39 M7 U35 non-standard No Details →
3.1.18 18 Jun 2021 C4 H39 M7 U35 non-standard No Details →
3.1.17 14 May 2021 C4 H39 M7 U35 non-standard No Details →
3.1.16 13 May 2021 C4 H39 M7 U35 non-standard No Details →
3.1.15 21 Apr 2021 C4 H39 M7 U35 non-standard No Details →
3.1.14 28 Feb 2021 C4 H39 M7 U35 non-standard No Details →
3.1.13 09 Feb 2021 C4 H39 M7 U35 non-standard No Details →
3.1.12 06 Jan 2021 C4 H39 M7 U35 non-standard No Details →
3.1.11 23 Oct 2020 C4 H39 M7 U35 non-standard No Details →
3.1.10 23 Oct 2020 C4 H39 M7 U35 non-standard No Details →
3.1.9 01 Oct 2020 C4 H39 M7 U35 non-standard No Details →
3.1.8 04 Sep 2020 C4 H39 M7 U35 non-standard No Details →
3.1.7 13 Jul 2020 C4 H39 M7 U35 non-standard No Details →
3.1.6 13 Jul 2020 C4 H39 M7 U35 non-standard No Details →
3.1.5 12 Jul 2020 C4 H39 M7 U35 non-standard No Details →
3.1.4 12 Jul 2020 C4 H39 M7 U35 non-standard No Details →
3.1.3 31 May 2020 C4 H39 M7 U35 non-standard No Details →
3.1.2 05 May 2020 C4 H39 M7 U35 non-standard No Details →
3.1.1 11 Apr 2020 C4 H39 M7 U35 non-standard No Details →
3.1.0 24 Feb 2020 C4 H39 M7 U35 non-standard No Details →
3.0.9 24 Feb 2020 C4 H39 M7 U35 non-standard No Details →
2.1.15 17 Feb 2020 C4 H39 M7 U35 non-standard No Details →
3.0.8 17 Feb 2020 C4 H39 M7 U35 non-standard No Details →
3.0.7 08 Feb 2020 C4 H39 M7 U35 non-standard No Details →
3.0.6 08 Feb 2020 C4 H39 M7 U35 non-standard No Details →
3.0.5 14 Nov 2019 C4 H39 M7 U35 non-standard No Details →
3.0.4 22 Oct 2019 C4 H39 M7 U35 non-standard No Details →
3.0.3 02 Oct 2019 C4 H39 M7 U35 non-standard No Details →
3.0.2 22 Aug 2019 C4 H39 M7 U35 non-standard No Details →
3.0.1 15 Aug 2019 C4 H39 M7 U35 non-standard No Details →
2.1.14 14 Aug 2019 C4 H39 M7 U35 non-standard No Details →
3.0.0 12 Aug 2019 C4 H39 M7 U35 non-standard No Details →
2.1.13 29 Jul 2019 C4 H39 M7 U35 non-standard No Details →
2.1.12 21 Jul 2019 C4 H39 M7 U35 non-standard No Details →
2.1.11 15 Jul 2018 C4 H39 M7 U35 non-standard No Details →
2.1.10 19 May 2018 C4 H39 M7 U35 non-standard No Details →
2.1.9 24 Mar 2018 C4 H39 M7 U35 non-standard No Details →
2.1.8 11 Dec 2017 C4 H39 M7 U35 non-standard No Details →
2.1.7 28 Sep 2017 C4 H39 M7 U35 non-standard No Details →
2.1.6 25 Sep 2017 C4 H39 M7 U35 non-standard No Details →
2.1.5 10 Jun 2017 C4 H39 M7 U35 non-standard No Details →
2.1.4 10 Jun 2017 C4 H39 M7 U35 non-standard No Details →
2.1.3 08 Mar 2017 C4 H39 M7 U35 non-standard No Details →
2.1.1 08 Dec 2016 C4 H39 M7 U35 non-standard No Details →
2.1.0 22 Oct 2016 C4 H39 M7 U35 non-standard No Details →
2.0.9 16 Oct 2016 C4 H39 M7 U35 non-standard No Details →
2.0.9.dev1 16 Oct 2016 C4 H39 M7 U35 non-standard No Details →
2.0.9.dev0 09 Oct 2016 C4 H39 M7 U35 non-standard No Details →
2.0.8 03 Aug 2016 C4 H39 M7 U35 non-standard No Details →
2.0.7 17 Jul 2016 C4 H39 M7 U35 non-standard No Details →
2.0.6 20 Jun 2016 C4 H39 M7 U35 non-standard No Details →
2.0.5 30 May 2016 C4 H39 M7 U35 non-standard No Details →
2.0.4 30 May 2016 C4 H39 M7 U35 non-standard No Details →
2.0.3 24 May 2016 C4 H39 M7 U35 non-standard No Details →
2.0.2 28 Apr 2016 C4 H39 M7 U35 non-standard No Details →
2.0.1 24 Apr 2016 C4 H39 M7 U35 non-standard No Details →
2.0.0 22 Apr 2016 C4 H39 M7 U35 non-standard No Details →
1.0.2 11 Feb 2016 C4 H39 M7 U35 — No Details →
1.0.1 30 Apr 2015 C4 H39 M7 U35 — No Details →
1.0.0 08 Apr 2015 C4 H39 M7 U35 — No Details →
0.3.7 08 Apr 2015 C4 H39 M7 U35 — No Details →
0.3.6 22 Jan 2015 C4 H39 M7 U35 — No Details →
0.3.5 12 Jan 2015 C4 H39 M7 U35 — No Details →
0.3.4 06 Jan 2015 C4 H39 M7 U35 — No Details →
0.3.3 04 Jan 2015 C4 H39 M7 U35 — No Details →
0.3.2.1 18 Nov 2014 C4 H39 M7 U35 — No Details →
0.3.2 14 Nov 2014 C4 H39 M7 U35 — No Details →
0.3.2rc1 06 Jul 2011 C5 H39 M7 U33 — No Details →
0.3.1b2 17 Jan 2011 C5 H39 M7 U33 — No Details →
0.3.0b2 09 Jul 2010 C5 H39 M7 U33 — No Details →
0.3.0b1 08 Jul 2010 C5 H39 M7 U33 — No Details →
0.2.0b1 25 May 2010 C5 H39 M7 U33 — No Details →
0.1.7 21 Mar 2010 C4 H39 M7 U35 — No Details →

All 116 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 2
  • 2023 6
  • 2024 2
  • 2026 81

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

03 Vulnerabilities

Recorded vulnerabilities for gitpython

The 5 most severe of 91 vulnerabilities recorded for this package

Search all 91 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Critical Vulnerability in GitPython: Bypass of Unsafe Clone Option Gate 9.8 critical No fix published 01 Aug 2026
CVE-2023-40267: GitPython Remote Code Execution Vulnerability 9.8 critical 3.1.32 11 Aug 2023
Critical RCE Vulnerability in GitPython: Multi-Line Config Corruption 9.8 critical No fix published 25 Aug 2026
CVE-2026-42284: GitPython Vulnerability Allows Execution of Attacker Hooks During Clone 9.8 critical 3.1.47 07 May 2026
CVE-2026-78676: GitPython Critical Vulnerability Leading to Remote Code Execution via Config Injection 9.8 critical 3.1.59 08 Sep 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 gitpython

Is gitpython safe to use?

Vulert records 91 vulnerabilities for gitpython in PyPI: 5 critical, 42 high, 8 medium and 0 low, plus 36 not yet rated. 17 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is gitpython's Vulert package health score?

Vulert scores gitpython 50/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 gitpython affected?

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

Which version of gitpython should I use?

3.2.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 gitpython have?

91 vulnerabilities are recorded for gitpython in the PyPI ecosystem: 5 critical, 42 high, 8 medium and 0 low, plus 36 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 gitpython vulnerabilities disclosed?

81 vulnerabilities were recorded for gitpython in the last 12 months, and the oldest entry in this database dates to 06 Dec 2022. 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 gitpython 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 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.