Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

gitpython vulnerabilities and fixes

Recent CVEs affecting gitpython, with upgrade or downgrade steps. 14 tracked.

gitpython has 14 tracked vulnerabilities, 1 critical. A fixed release or vendor patch exists for 14. Most recent: 2026-08-19. Highest priority: CVE-2026-67324 (score 60/100).

FAQ

How do I fix gitpython vulnerabilities?

Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.

Is gitpython being exploited right now?

None of the tracked gitpython CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.

Which gitpython CVE should I patch first?

CVE-2026-67324 currently ranks highest (60/100): GitPython 3.1.50 fails to recognize joined short-option forms such as -u<value> (the short form of --upload-pa.

← Back to latest CVEs