How many CVEs have patched remove?

2 published CVEs changed remove in gitpython-developers/GitPython, in 2 distinct patches totalling 11 changed lines, between 2026 and 2026.

What is the latest CVE that changed remove?

CVE-2026-76222 (GitPython before 3.1.58 Path Traversal via .gitmodules Submodule Name), published 2026-08-19, changed lines 1179 of git/objects/submodule/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

Log in Create an account

gitpython-developers/GitPython

Function

2 files

remove

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

Defined in 2 files

Last patched August 19, 2026

2

CVEs

That changed this function

2

Distinct patches

Backports counted once

11

Lines changed

Added plus removed

2026

Years

By CVE publication date

Overview

remove in gitpython-developers/GitPython was changed by 2 published CVE fixes in 2026, in 2 distinct patches that added or removed 11 lines in total.

The name occurs in 2 files: git/index/base.py, git/objects/submodule/base.py.

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

CVEs that patched it

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

GitPython before 3.1.58 Path Traversal via .gitmodules Submodule Name
CVE-2026-76222 · git/objects/submodule/base.py · line 1179 · +1 −0
High · CVSS 8.4
EPSS 0.4%2026-08-19
GitPython before 3.1.58 Arbitrary File Read via pathspec-from-file
CVE-2026-76217 · git/index/base.py · lines 1027–1077 · +10 −0 in 3 hunks
High · CVSS 7.1
EPSS 0.4%2026-08-19

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 files that CVE fixes also changed.

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 remove.

How many CVEs have patched remove?: 2 published CVEs changed remove in gitpython-developers/GitPython, in 2 distinct patches totalling 11 changed lines, between 2026 and 2026.
What is the latest CVE that changed remove?: CVE-2026-76222 (GitPython before 3.1.58 Path Traversal via .gitmodules Submodule Name), published 2026-08-19, changed lines 1179 of git/objects/submodule/base.py.
How does remove compare to the rest of gitpython-developers/GitPython?: gitpython-developers/GitPython has 18 CVEs with a located fix in total; 2 of them changed remove.
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

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