How many CVEs have patched Repo?

4 published CVEs changed Repo in gitpython-developers/GitPython, in 4 distinct patches totalling 30 changed lines, between 2022 and 2026.

What is the latest CVE that changed Repo?

CVE-2026-78679 (GitPython before 3.1.59 Arbitrary File Read via TagReference.create), published 2026-08-25, changed lines 202 to 214 of git/repo/base.py.

What do the line numbers refer to?

Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

RadicalNotion.AI

Security data

Weaknesses (CWE)The MITRE CWE weakness catalog
Attack Patterns (CAPEC)MITRE CAPEC attack patterns
CNAsNumbering authorities and report cards
VendorsVulnerabilities by vendor
Patched FunctionsWhere CVE fixes land in code

Tools

CVSS CalculatorScore CVSS 4.0, 3.1, 3.0 & 2.0
Badge BuilderEmbeddable SVG badges for READMEs

Resources

LearnSecurity guides
Data SourcesCVE data sources

About Blog Pricing Demo

Home
Patched Functions
Gitpython Developers
Gitpython
Repo

RadicalNotion.AI

We do not sell or share your personal information.

Security Data

CWE Directory
CAPEC Directory
CNA Directory
CNA Leaderboard
CNA Report Cards
Vendor Directory
Patched Functions
Data Sources

Calculators

CVSS Calculator
CVSS 4.0
CVSS 3.1
CVSS 3.0
CVSS 2.0
Badge Builder

Platform

My Vulnerabilities
Insights
Notifications
Pricing

Learn

Guides
What is a CVE?
What is CVSS?
The CISA KEV catalog
What is EPSS?

Company

About
Blog
Careers
Contact
Demo

Account

Legal

Security
Privacy
Terms

RadicalNotion.AI

Security data

Weaknesses (CWE)The MITRE CWE weakness catalog
Attack Patterns (CAPEC)MITRE CAPEC attack patterns
CNAsNumbering authorities and report cards
VendorsVulnerabilities by vendor
Patched FunctionsWhere CVE fixes land in code

Tools

CVSS CalculatorScore CVSS 4.0, 3.1, 3.0 & 2.0
Badge BuilderEmbeddable SVG badges for READMEs

Resources

LearnSecurity guides
Data SourcesCVE data sources

About Blog Pricing Demo

Home
Patched Functions
Gitpython Developers
Gitpython
Repo

Repo in gitpython-developers/GitPython: Patched by 4 CVEs

gitpython-developers/GitPython

Class

Repo

Name: Repo in gitpython-developers/GitPython: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

git/repo/base.py

Last patched August 25, 2026

CVEs

That changed this function

Distinct patches

Backports counted once

Lines changed

Added plus removed

2022–2026

Years

By CVE publication date

Overview

Repo in gitpython-developers/GitPython was changed by 4 published CVE fixes between 2022 and 2026, in 4 distinct patches that added or removed 30 lines in total.

gitpython-developers/GitPython has 18 CVEs with a located fix in total, so 22% of them touched this function.

CVEs that patched it

Every published CVE whose fix changed Repo, newest first, with the lines each fix touched.

GitPython before 3.1.59 Arbitrary File Read via TagReference.create
CVE-2026-78679 · lines 202–214 · +13 −0
High · CVSS 7.1
EPSS 0.3%2026-08-25
GitPython before 3.1.59 Path Traversal via separate-git-dir
CVE-2026-78677 · lines 162–163 · +2 −0
High · CVSS 8.7
EPSS 0.7%2026-08-25
GitPython before 3.1.51 Command Injection via unguarded Git options
CVE-2026-67323 · lines 164–177 · +14 −0
High · CVSS 8.6
EPSS 1.3%2026-08-01
GitPython vulnerable to Remote Code Execution due to improper user input validation
CVE-2022-24439 · line 136 · +1 −0
Critical · CVSS 9.2
EPSS 5.9%2022-12-12

Get an alert when the next CVE fix lands in gitpython-developers/GitPython, with the patched functions.

Monitor GitPython CVEs

Other functions in these files

Functions in the same file that CVE fixes also changed.

1_clonegit/repo/base.py4 CVEs · 4 patches2023 to 2026
2blame_incrementalgit/repo/base.py2 CVEs · 2 patches2026
3blamegit/repo/base.py2 CVEs · 2 patches2026
4doesgit/repo/base.py1 CVEs · 1 patches2026
5_get_alternatesgit/repo/base.py1 CVEs · 1 patches2026
6__init__git/repo/base.py1 CVEs · 1 patches2026
7iter_commitsgit/repo/base.py1 CVEs · 1 patches2026
8archivegit/repo/base.py1 CVEs · 1 patches2026

Other hotspots in the repository

Functions in gitpython-developers/GitPython changed by the most CVE fixes.

_clone4 CVEs · git/repo/base.py execute2 CVEs · git/cmd.py blame_incremental2 CVEs · git/repo/base.py ls_remote2 CVEs · git/cmd.py check_unsafe_options2 CVEs · git/cmd.py blame2 CVEs · git/repo/base.py

All patched functions in gitpython-developers/GitPython

Frequently asked questions

Common questions about CVE fixes to Repo.

How many CVEs have patched Repo?: 4 published CVEs changed Repo in gitpython-developers/GitPython, in 4 distinct patches totalling 30 changed lines, between 2022 and 2026.
What is the latest CVE that changed Repo?: CVE-2026-78679 (GitPython before 3.1.59 Arbitrary File Read via TagReference.create), published 2026-08-25, changed lines 202 to 214 of git/repo/base.py.
How does Repo compare to the rest of gitpython-developers/GitPython?: gitpython-developers/GitPython has 18 CVEs with a located fix in total; 4 of them changed Repo.
What do the line numbers refer to?: Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

References

git/repo/base.py on GitHub (opens in a new tab)
All patched functions in gitpython-developers/GitPython
Patched functions directory

Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.

Track gitpython-developers/GitPython CVEs

Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.

Create an account See pricing

On this page

Overview
CVEs that patched it
Other functions in these files
Other hotspots in the repository
FAQ
References