CVE-2026-44243
Description
A flaw was found in GitPython, a Python library used to interact with Git repositories. This vulnerability allows attackers to supply a specially crafted reference path to an application utilizing GitPython. Due to insufficient validation of these paths during reference creation, renaming, or deletion, an attacker can write, overwrite, move, or delete files outside the intended Git repository directory. This could lead to unauthorized modification or deletion of critical system files.
Statement
This flaw in GitPython is rated as Moderate as it allows an attacker to perform arbitrary file write, overwrite, move, or delete operations outside of a Git repository. This is possible by supplying a crafted reference path to an application that uses GitPython, leading to potential unauthorized modification or deletion of critical system files. The impact is significant due to the potential for data integrity compromise on systems utilizing affected GitPython versions. However, exploitation is unlikely as it requires an application to use GitPython affected functions with user-supplied data. The vulnerability is not automatically exploitable simply because GitPython is installed or used. It requires to pass user-controlled data into the affected functions - thus AC:H.
Mitigation
Applications using GitPython should validate and sanitize all reference path inputs before passing them to GitPython's reference creation, rename, and delete APIs. Specifically, reject any reference path containing path traversal sequences such as "..". In Red Hat products, exploitation requires the ability to supply a crafted Git reference name to an application using GitPython — environments that do not expose GitPython reference operations to untrusted user input are not susceptible to this attack. Updating to GitPython 3.1.48 or later fully resolves this issue.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 6.3 | 7.1 | N/A |
| Attack Vector | Local | Local | N/A |
| Attack Complexity | High | Low | N/A |
| Privileges Required | Low | Low | N/A |
| User Interaction | None | None | N/A |
| Scope | Unchanged | Unchanged | N/A |
| Confidentiality | None | None | N/A |
| Integrity Impact | High | High | N/A |
| Availability Impact | High | High | N/A |
Vector
Red Hat: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:H
NVD: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
Understanding the Weakness (CWE)
Integrity,Confidentiality,Availability
Technical Impact: Execute Unauthorized Code or Commands
The attacker may be able to create or overwrite critical files that are used to execute code, such as programs or libraries.
Integrity
Technical Impact: Modify Files or Directories
The attacker may be able to overwrite or create critical files, such as programs, libraries, or important data. If the targeted file is used for a security mechanism, then the attacker may be able to bypass that mechanism. For example, appending a new account at the end of a password file may allow an attacker to bypass authentication.
Confidentiality
Technical Impact: Read Files or Directories
The attacker may be able read the contents of unexpected files and expose sensitive data. If the targeted file is used for a security mechanism, then the attacker may be able to bypass that mechanism. For example, by reading a password file, the attacker could conduct brute force password guessing attacks in order to break into an account on the system.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
The attacker may be able to overwrite, delete, or corrupt unexpected critical files such as programs, libraries, or important data. This may prevent the product from working at all and in the case of protection mechanisms such as authentication, it has the potential to lock out product users.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
