How many CVEs have patched ls_remote?

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

What is the latest CVE that changed ls_remote?

CVE-2026-78679 (GitPython before 3.1.59 Arbitrary File Read via TagReference.create), published 2026-08-25, changed lines 1139 of git/cmd.py.

How does ls_remote compare to the rest of gitpython-developers/GitPython?

gitpython-developers/GitPython has 18 CVEs with a located fix in total; 2 of them changed ls_remote.

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

ls_remote

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

git/cmd.py

Last patched August 25, 2026

2

CVEs

That changed this function

2

Distinct patches

Backports counted once

18

Lines changed

Added plus removed

2026

Years

By CVE publication date

Overview

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

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 ls_remote, newest first, with the lines each fix touched.

GitPython before 3.1.59 Arbitrary File Read via TagReference.create
CVE-2026-78679 · line 1139 · +1 −1
High · CVSS 7.1
EPSS 0.3%2026-08-25
GitPython before 3.1.51 Command Injection via unguarded Git options
CVE-2026-67323 · lines 1101–1116 · +16 −0
High · CVSS 8.6
EPSS 1.3%2026-08-01

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.

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 check_unsafe_options2 CVEs · git/cmd.py blame2 CVEs · git/repo/base.py _option_candidates2 CVEs · git/cmd.py

All patched functions in gitpython-developers/GitPython

Frequently asked questions

Common questions about CVE fixes to ls_remote.

How many CVEs have patched ls_remote?: 2 published CVEs changed ls_remote in gitpython-developers/GitPython, in 2 distinct patches totalling 18 changed lines, between 2026 and 2026.
What is the latest CVE that changed ls_remote?: CVE-2026-78679 (GitPython before 3.1.59 Arbitrary File Read via TagReference.create), published 2026-08-25, changed lines 1139 of git/cmd.py.
How does ls_remote compare to the rest of gitpython-developers/GitPython?: gitpython-developers/GitPython has 18 CVEs with a located fix in total; 2 of them changed ls_remote.
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