Metrics
Affected Vendors & Products
No advisories yet.
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Tue, 04 Aug 2026 00:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-88 | |
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
Mon, 03 Aug 2026 21:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Sun, 02 Aug 2026 21:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Gitpython-developers
Gitpython-developers gitpython |
|
| Vendors & Products |
Gitpython-developers
Gitpython-developers gitpython |
Sat, 01 Aug 2026 12:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | GitPython before 3.1.51 fails to guard against dangerous Git options passed as keyword arguments in Repo.archive() and git.ls_remote(), allowing command injection via options such as --exec/--upload-pack (leading to arbitrary command execution). Additionally, Repo.iter_commits() and Repo.blame() do not check for leading-dash revision arguments, so a revision like --output=<path> can cause Git to open and truncate an arbitrary file. Exploitation requires an application that passes attacker-controlled arguments to these methods. | |
| Title | GitPython before 3.1.51 Command Injection via unguarded Git options | |
| Weaknesses | CWE-77 | |
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: VulnCheck
Published:
Updated: 2026-08-05T03:56:21.674Z
Reserved: 2026-07-29T13:07:21.183Z
Link: CVE-2026-67323
Updated: 2026-08-03T19:41:27.538Z
Status : Received
Published: 2026-08-01T13:17:02.637
Modified: 2026-08-05T05:17:11.013
Link: CVE-2026-67323
OpenCVE Enrichment
Updated: 2026-08-04T11:15:06Z