Evidence used
- No CISA KEV confirmation is currently recorded.
- A structured source references public exploit or proof-of-concept material.
- EPSS is 0.36% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2026
CVE-2026-73621High confidence
GitPython before 3.1.56 Arbitrary File Truncation via Commit.count
gitpython-developers · GitPython
Official source article: GitHub GHSA-P538-C434-8V24 ↗. Check the applicable product and release in the original source.
5.3MediumCVSS 4.0
Patch only the product branches with a verified fix
Fix availability varies by productMedium technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 53 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityMedium→Operational priority:High, raised one band.upgradedsince 14 Aug 2026
Compensating controls
- Validate the affected product branch and deploy the verified fixed release.
- Restrict the affected network interface to trusted sources where business-safe.
- Increase monitoring for the attack path and post-exploitation behaviour described in the report.
Verification
- Confirm that the asset runs gitpython-developers GitPython and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Remediation availability differs by product scope
Verified remediation exists for at least one product or source, but 53 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
- Red Hat Product Security: 51 affected or under-investigation product states without a fixed product state in the same current advisory
- Debian Security Tracker: 2 affected package states with no published fix
Distribution package intelligence
5 package statesRelease-specific package status
Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
Package result overrides the generic status
BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 2 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.
Repository candidate not checked
A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.
| Distribution release | Source package | Vendor state | Fixed version | Evidence |
|---|---|---|---|---|
| Debian trixietrixie · source | python-git | Affected, no fix publishedDebian currently tracks this release as open. | Not published in this feed | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Debian bookwormbookworm · source | python-git | Affected, no fix publishedDebian currently tracks this release as open. | Not published in this feed | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Debian forkyforky · source | python-git | Vendor fix publishedDebian records a fixed source-package version for this release. | 3.1.61-1 | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Debian sidsid · source | python-git | Vendor fix publishedDebian records a fixed source-package version for this release. | 3.1.61-1 | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Ubuntu 24.04 LTSnoble · esm-apps | python-git | Under evaluationCanonical reports that the package might be affected and still needs evaluation or fixing. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
Open-source package ranges2 source-attributed ranges
These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.
| Ecosystem and package | Affected range | First fixed version | Evidence |
|---|---|---|---|
| PyPIgitpython | ECOSYSTEM: introduced 0; fixed 3.1.56 | 3.1.56 | OSV record ↗aggregator derived · 10 Sep 2026 |
| PyPIgitpython | ECOSYSTEM: introduced 0; fixed 3.1.56 | 3.1.56 | OSV record ↗source linked ecosystem record · 10 Sep 2026 |
Direct vendor intelligence
2 currentAuthoritative vendor CSAF and VEX advisories
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
CVE-2026-73621 · CSAF 2.0 · revision 6 · interimSUSE Product Security TeamCVE-2026-73621
The vendor recommends these product versions as the target state.
- python311-GitPython-3.1.34.1693646983.2a2ae77-150400.9.8.1 as component of SUSE Linux Enterprise Desktop 15 SP7
- python311-GitPython-3.1.34.1693646983.2a2ae77-150400.9.8.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP4-ESPOS
- python311-GitPython-3.1.34.1693646983.2a2ae77-150400.9.8.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
- python311-GitPython-3.1.34.1693646983.2a2ae77-150400.9.8.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS
- python311-GitPython-3.1.34.1693646983.2a2ae77-150400.9.8.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS
- python311-GitPython-3.1.34.1693646983.2a2ae77-150400.9.8.1 as component of SUSE Linux Enterprise Module for Python 3 15 SP7
- python311-GitPython-3.1.34.1693646983.2a2ae77-150400.9.8.1 as component of SUSE Linux Enterprise Server 15 SP4-LTSS
- python311-GitPython-3.1.34.1693646983.2a2ae77-150400.9.8.1 as component of SUSE Linux Enterprise Server 15 SP4-TERADATA
- python311-GitPython-3.1.34.1693646983.2a2ae77-150400.9.8.1 as component of SUSE Linux Enterprise Server 15 SP5-LTSS
- python311-GitPython-3.1.34.1693646983.2a2ae77-150400.9.8.1 as component of SUSE Linux Enterprise Server 15 SP6-LTSS
- python311-GitPython-3.1.34.1693646983.2a2ae77-150400.9.8.1 as component of SUSE Linux Enterprise Server 15 SP7
- python313-GitPython-3.1.44-160000.4.1 as component of SUSE Linux Enterprise Server 16.0
- Summary
- GitPython before 3.1.56 contains an argument injection vulnerability in the Commit.count() method, which forwards keyword arguments to 'git rev-list' without the check_unsafe_options guard present in the sibling iter_items method. An attacker who can control options passed to Commit.count (e.g., via an application that forwards a user-supplied options dict) can supply output= , causing 'git rev-list --output= ' to open and truncate the target file to zero bytes before revision parsing. This allows destruction/blanking of an arbitrary file at the process's privilege level (no content control, 0-byte truncation).
- Remediation
- To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2026-73621 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitygitpython: GitPython: Arbitrary File Truncation via Commit.count() Argument Injection
The vendor explicitly identifies these products as affected by this CVE.
- exploit-intelligence-tech-preview/vulnerability-analysis-rhel9 as a component of Exploit Intelligence
- mta/mta-solution-server-rhel9 as a component of Migration Toolkit for Applications 8
- pen-drive/pen-drive-scanner-rhel9 as a component of Pen Drive Powered by Red Hat Lightspeed
- rhaiis/vllm-cpu-rhel9 as a component of Red Hat AI Inference Server
- rhaiis/vllm-tpu-rhel9 as a component of Red Hat AI Inference Server
- ansible-automation-platform-24/controller-rhel8 as a component of Red Hat Ansible Automation Platform 2
- ansible-automation-platform-24/hub-rhel8 as a component of Red Hat Ansible Automation Platform 2
- ansible-automation-platform-25/controller-rhel8 as a component of Red Hat Ansible Automation Platform 2
- ansible-automation-platform-25/hub-rhel8 as a component of Red Hat Ansible Automation Platform 2
- ansible-automation-platform-26/controller-rhel9 as a component of Red Hat Ansible Automation Platform 2
- ansible-automation-platform-26/hub-rhel9 as a component of Red Hat Ansible Automation Platform 2
- ansible-automation-platform-27/controller-rhel9 as a component of Red Hat Ansible Automation Platform 2
- Summary
- A flaw was found in GitPython. An argument injection vulnerability in the `Commit.count()` method allows an attacker to control options passed to the method. By supplying a crafted `output` option, an attacker can cause the `git rev-list` command to truncate an arbitrary file to zero bytes. This enables the destruction or blanking of files at the process's privilege level, leading to data loss.
- Remediation
- Fix deferred
Medium technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 53 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
Fix availability varies by product01
What, why and how
GitPython before 3.1.56 contains an argument injection vulnerability in the Commit.count() method, which forwards keyword arguments to 'git rev-list' without the check_unsafe_options guard present in the sibling iter_items method. An attacker who can control options passed to Commit.count (e.g., via an application that forwards a user-supplied options dict) can supply output=<path>, causing 'git rev-list --output=<path>' to open and truncate the target file to zero bytes before revision parsing. This allows destruction/blanking of an arbitrary file at the process's privilege level (no content control, 0-byte truncation).
What
GitPython before 3.1.56 contains an argument injection vulnerability in the Commit.count() method, which forwards keyword arguments to 'git rev-list' without the check_unsafe_options guard present in the sibling iter_items method. An attacker who can control options passed to Commit.count (e.g., via an application that forwards a user-supplied options dict) can supply output=<path>, causing 'git rev-list --output=<path>' to open and truncate the target file to zero bytes before revision parsing. This allows destruction/blanking of an arbitrary file at the process's privilege level (no content control, 0-byte truncation).
Why
The product constructs a string for a command to be executed by a separate component in another control sphere, but it does not properly delimit the intended arguments, options, or switches within that command string.
How
An attacker operating through a network path may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
What
GitPython before 3.1.56 contains an argument injection vulnerability in the Commit.count() method, which forwards keyword arguments to 'git rev-list' without the check_unsafe_options guard present in the sibling iter_items method. An attacker who can control options passed to Commit.count (e.g., via an application that forwards a user-supplied options dict) can supply output=<path>, causing 'git rev-list --output=<path>' to open and truncate the target file to zero bytes before revision parsing. This allows destruction/blanking of an arbitrary file at the process's privilege level (no content control, 0-byte truncation).
Why
The product constructs a string for a command to be executed by a separate component in another control sphere, but it does not properly delimit the intended arguments, options, or switches within that command string.
How
An attacker operating through a network path may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material Reference recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.A structured CVE source labels at least one public reference as exploit material. BlackTree has not independently validated that it is safe, reliable or weaponised.
- Likely attack path
- a network path → Improper Neutralization of Argument Delimiters in a Command ('Argument Injection') → cause the confidentiality, integrity or availability impact described by the vendor
- Attack surface
- Network
- Privileges required
- Low: a basic authenticated account is required
- User interaction
- None
- Attack complexity
- Low: no specialised conditions are recorded
- Security boundary
- Not a CVSS 4.0 base metric
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-88 ↗
CWE-88: Improper Neutralization of Argument Delimiters in a Command ('Argument Injection'). The product constructs a string for a command to be executed by a separate component in another control sphere, but it does not properly delimit the intended arguments, options, or switches within that command string.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:NCommon Vulnerability Scoring System 4.0: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.ATNoneAttack requirements: No additional deployment or execution condition is required.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.VCNoneVulnerable-system confidentiality: No direct loss is represented by this metric.VILowVulnerable-system integrity: A successful attack can cause a limited loss.VALowVulnerable-system availability: A successful attack can cause a limited loss.SCNoneSubsequent-system confidentiality: No direct loss is represented by this metric.SINoneSubsequent-system integrity: No direct loss is represented by this metric.SANoneSubsequent-system availability: No direct loss is represented by this metric.- Post-exploitation / living off the land
- No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Fix availability varies by product
- Affected
- GitPython: < 3.1.56
- Fixed
- GitPython: 3.1.56
- Action
- Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
- Workaround
- No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
Official vendor articles1 stored document
Linked articles are downloaded and versioned as source evidence. A CVE mention or approved update relationship does not, by itself, verify a fix for every product branch.
- Arbitrary file truncation via git rev-list --output argument injection in unguarded Commit.count · Advisory · gitpython-developers/GitPython · GitHub →Original publisher ↗Searchable text snapshot · Captured 27 Sep 2026gitpython-developers / GitPython Public Uh oh! There was an error while loading. Please reload this page . Notifications You must be signed in to change notification settings Fork 1k Star 5.2k Code Issues 6 Pull requests 1 Discussions Actions Security and quality 35 Insights Additional navigation option
04
Evidence and provenance
Published 13 Aug 2026 · Last source change 14 Aug 2026, 18:10 UTC · CWE-88 · Improper Neutralization of Argument Delimiters in a Command ('Argument Injection')
CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source FIRST · tracked since 2026-08-14
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2026-57825
Product sourceCNA
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceCNA
NVD statusNVD enriched
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
- Affected versionsThe structured affected or fixed version information changed.Red Hat Product Security ↗
- Before
- exploit-intelligence-tech-preview/vulnerability-analysis-rhel9 as a component of Exploit Intelligence; mta/mta-solution-server-rhel9 as a component of Migration Toolkit for Applications 8; pen-drive/pen-drive-scanner-rhel9 as a component of Pen Drive Powered by Red Hat Lightspeed; rhaiis/vllm-cpu-rhel9 as a component of Red Hat AI Inference Server; rhaiis/vllm-tpu-rhel9 as a component of Red Hat AI Inference Server; ansible-automation-platform-24/controller-rhel8 as a component of Red Hat Ansible Automation Platform 2; ansible-automation-platform-24/hub-rhel8 as a component of Red Hat Ansible Automation Platform 2; ansible-automation-platform-25/controller-rhel8 as a component of Red Hat Ansible Automation Platform 2; ansible-automation-platform-25/hub-rhel8 as a component of Red Hat Ansible Automation Platform 2; ansible-automation-platform-26/controller-rhel9 as a component of Red Hat Ansible Automation Platform 2; ansible-automation-platform-26/hub-rhel9 as a component of Red Hat Ansible Automation Platform 2; ansible-automation-platform-27/controller-rhel9 as a component of Red Hat Ansible Automation Platform 2; ansible-automation-platform-27/hub-rhel9 as a component of Red Hat Ansible Automation Platform 2; python-gitpython.src as a component of Red Hat Ansible Automation Platform 2; rhelai3/bootc-cuda-rhel9 as a component of Red Hat Enterprise Linux AI (RHEL AI) 3; rhelai3/bootc-gaudi-rhel9 as a component of Red Hat Enterprise Linux AI (RHEL AI) 3; rhelai3/bootc-rocm-rhel9 as a component of Red Hat Enterprise Linux AI (RHEL AI) 3; rhelai3/disk-image-cuda-rhel9 as a component of Red Hat Enterprise Linux AI (RHEL AI) 3; rust.src as a component of Red Hat Hardened Images; rhoai/odh-feature-server-rhel9 as a component of Red Hat OpenShift AI (RHOAI); rhoai/odh-mlflow-rhel9 as a component of Red Hat OpenShift AI (RHOAI); rhoai/odh-pipeline-runtime-datascience-cpu-py312-rhel9 as a component of Red Hat OpenShift AI (RHOAI); rhoai/odh-pipeline-runtime-pytorch-cuda-py312-rhel9 as a component of Red Hat OpenShift AI (RHOAI); rhoai/odh-pipeline-runtime-pytorch-llmcompressor-cuda-py312-rhel9 as a component of Red Hat OpenShift AI (RHOAI); rhoai/odh-pipeline-runtime-pytorch-rocm-py312-rhel9 as a component of Red Hat OpenShift AI (RHOAI); rhoai/odh-pipeline-runtime-tensorflow-cuda-py312-rhel9 as a component of Red Hat OpenShift AI (RHOAI); rhoai/odh-pipeline-runtime-tensorflow-rocm-py312-rhel9 as a component of Red Hat OpenShift AI (RHOAI); rhoai/odh-th06-cpu-torch210-py312-rhel9 as a component of Red Hat OpenShift AI (RHOAI); rhoai/odh-th06-cpu-torch291-py312-rhel9 as a component of Red Hat OpenShift AI (RHOAI); rhoai/odh-th06-cuda130-torch210-py312-rhel9 as a component of Red Hat OpenShift AI (RHOAI); and 22 more
- After
- exploit-intelligence-tech-preview/vulnerability-analysis-rhel9 as a component of Exploit Intelligence; mta/mta-solution-server-rhel9 as a component of Migration Toolkit for Applications 8; pen-drive/pen-drive-scanner-rhel9 as a component of Pen Drive Powered by Red Hat Lightspeed; rhaiis/vllm-cpu-rhel9 as a component of Red Hat AI Inference Server; rhaiis/vllm-tpu-rhel9 as a component of Red Hat AI Inference Server; ansible-automation-platform-24/controller-rhel8 as a component of Red Hat Ansible Automation Platform 2; ansible-automation-platform-24/hub-rhel8 as a component of Red Hat Ansible Automation Platform 2; ansible-automation-platform-25/controller-rhel8 as a component of Red Hat Ansible Automation Platform 2; ansible-automation-platform-25/hub-rhel8 as a component of Red Hat Ansible Automation Platform 2; ansible-automation-platform-26/controller-rhel9 as a component of Red Hat Ansible Automation Platform 2; ansible-automation-platform-26/hub-rhel9 as a component of Red Hat Ansible Automation Platform 2; ansible-automation-platform-27/controller-rhel9 as a component of Red Hat Ansible Automation Platform 2; ansible-automation-platform-27/hub-rhel9 as a component of Red Hat Ansible Automation Platform 2; python-gitpython.src as a component of Red Hat Ansible Automation Platform 2; rhelai3/bootc-cuda-rhel9 as a component of Red Hat Enterprise Linux AI (RHEL AI) 3; rhelai3/bootc-gaudi-rhel9 as a component of Red Hat Enterprise Linux AI (RHEL AI) 3; rhelai3/bootc-rocm-rhel9 as a component of Red Hat Enterprise Linux AI (RHEL AI) 3; rhelai3/disk-image-cuda-rhel9 as a component of Red Hat Enterprise Linux AI (RHEL AI) 3; rhoai/odh-feature-server-rhel9 as a component of Red Hat OpenShift AI (RHOAI); rhoai/odh-mlflow-rhel9 as a component of Red Hat OpenShift AI (RHOAI); rhoai/odh-pipeline-runtime-datascience-cpu-py312-rhel9 as a component of Red Hat OpenShift AI (RHOAI); rhoai/odh-pipeline-runtime-pytorch-cuda-py312-rhel9 as a component of Red Hat OpenShift AI (RHOAI); rhoai/odh-pipeline-runtime-pytorch-llmcompressor-cuda-py312-rhel9 as a component of Red Hat OpenShift AI (RHOAI); rhoai/odh-pipeline-runtime-pytorch-rocm-py312-rhel9 as a component of Red Hat OpenShift AI (RHOAI); rhoai/odh-pipeline-runtime-tensorflow-cuda-py312-rhel9 as a component of Red Hat OpenShift AI (RHOAI); rhoai/odh-pipeline-runtime-tensorflow-rocm-py312-rhel9 as a component of Red Hat OpenShift AI (RHOAI); rhoai/odh-th06-cpu-torch210-py312-rhel9 as a component of Red Hat OpenShift AI (RHOAI); rhoai/odh-th06-cpu-torch291-py312-rhel9 as a component of Red Hat OpenShift AI (RHOAI); rhoai/odh-th06-cuda130-torch210-py312-rhel9 as a component of Red Hat OpenShift AI (RHOAI); rhoai/odh-th06-cuda130-torch291-py312-rhel9 as a component of Red Hat OpenShift AI (RHOAI); and 21 more
- Vendor guidanceAuthoritative vendor guidance changed: added vendor advisory: github.com/GHSA-p538-c434-8v24.disclosure@vulncheck.com ↗
- Before
- remediation: github.com/GHSA-p538-c434-8v24
- After
- remediation: github.com/GHSA-p538-c434-8v24 · vendor advisory: github.com/GHSA-p538-c434-8v24
- Public exploit evidencePublic exploit evidence changed from No public exploit to Public exploit reference.disclosure@vulncheck.com ↗
- Before
- No public exploit
- After
- Public exploit reference
CVE published
Fixed release or patch reference recorded
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.