How many CVEs have patched archive?

1 published CVEs changed archive in gitpython-developers/GitPython, in 1 distinct patches totalling 16 changed lines, between 2026 and 2026.

What is the latest CVE that changed archive?

CVE-2026-67323 (GitPython before 3.1.51 Command Injection via unguarded Git options), published 2026-08-01, changed lines 1636 to 1683 of git/repo/base.py.

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

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

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

archive

Name: archive 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 1, 2026

1

CVEs

That changed this function

1

Distinct patches

Backports counted once

16

Lines changed

Added plus removed

2026

Years

By CVE publication date

Overview

archive in gitpython-developers/GitPython was changed by 1 published CVE fixes in 2026, in 1 distinct patches that added or removed 16 lines in total.

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

CVEs that patched it

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

GitPython before 3.1.51 Command Injection via unguarded Git options
CVE-2026-67323 · lines 1636–1683 · +16 −0 in 3 hunks
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 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 archive.

How many CVEs have patched archive?: 1 published CVEs changed archive in gitpython-developers/GitPython, in 1 distinct patches totalling 16 changed lines, between 2026 and 2026.
What is the latest CVE that changed archive?: CVE-2026-67323 (GitPython before 3.1.51 Command Injection via unguarded Git options), published 2026-08-01, changed lines 1636 to 1683 of git/repo/base.py.
How does archive compare to the rest of gitpython-developers/GitPython?: gitpython-developers/GitPython has 18 CVEs with a located fix in total; 1 of them changed archive.
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