Skip to content
OpenAdvisories
Critical openSUSE-SU-2026:21874-1 26 CVEs

Security update for python-GitPython

Published Sep 18, 2026 · Updated Sep 25, 2026

Summary

This update for python-GitPython fixes the following issues:

- CVE-2026-67322: environment-variable exfiltration in `Repo.clone_from()` URL via os.path.expandvars() (bsc#1273357).
- CVE-2026-67323: unguarded Git options passed as keyword arguments in `Repo.archive()` and `git.ls_remote()` allow
for command injection (bsc#1273358).
- CVE-2026-67325: incomplete command injection blocklist fails to account for git's long-option prefix abbreviation
feature and allows for bypass (bsc#1273359).
- CVE-2026-67326: failure to validate newline characters in the section parameter of `config_writer()` can lead to
RCE via `core.hooksPath` (bsc#1273364).
- CVE-2026-69097: failure to properly escape section names in Git `config` files allows for injection of arbitrary
configuration directives through malicious submodule names and can lead to RCE (bsc#1273414).
- CVE-2026-73619: incomplete denylist in the `unsafe_git_archive_options` guard that omits `--add-file` and `--add-
virtual-file` options can lead to arbitrary file reads (bsc#1275755).
- CVE-2026-73620: failure to guard Git option forwarding in `IndexFile.checkout()` and `TagReference.create()` can lead
to arbitrary file reads and writes (bsc#1275756).
- CVE-2026-73621: argument injection in the `Commit.count()` method allows for destruction/blanking of arbitrary files
(bsc#1275757).
- CVE-2026-73622: failure to disable environment variable expansion in `Remote.create()` and `Submodule.add()` URL
handling allows for secret exfiltration via URLs containing variable references (bsc#1275751).
- CVE-2026-73623: incomplete denylist in `unsafe_git_clone_options` that omits `--template` allows for arbitrary command
execution (bsc#1275752).
- CVE-2026-73624: `Diffable.diff` method fails to validate git options passed through `kwargs`, which can lead to
arbitrary file writes (bsc#1275753).
- CVE-2026-73625: `check_unsafe_options` guard bypass via smuggling of git options inside single-character `kwarg`
values can lead to arbitrary code execution (bsc#1275754).
- CVE-2026-76217: failure to validate options passed to `git rm` and `git checkout` commands in `IndexFile.remove()`
and `Head.checkout()` can lead to arbitrary file reads (bsc#1275745).
- CVE-2026-76218: unguarded git option forwarding in `Repo.init` allows for arbitrary command execution (bsc#1275746).
- CVE-2026-76219: unguarded `git read-tree` option forwarding in `IndexFile.from_tree/reset/merge_tree` can lead to
arbitrary file overwrites (bsc#1275747).
- CVE-2026-76220: `check_unsafe_options` guard can be bypassed by combining a single-character `kwarg` with
`split_single_char_options=False`, which can lead to arbitrary OS command injection (bsc#1275748).
- CVE-2026-76221: `config-name` injection in the `option-name` validator can lead to remote code execution
(bsc#1275749).
- CVE-2026-76222: failure to validate submodule names from `.gitmodules` files allows creation of Git repositories at
arbitrary filesystem paths outside the intended clone directory (bsc#1275750).
- CVE-2026-78675: failure to disable `merge_includes` when parsing `.gitmodules` can lead to discloseure of local file
contents when arbitrary file paths are included via `[include]` directives (bsc#1276434).
- CVE-2026-78676: failure to safely re-serialize multi-line `git-config` values during write operations can corrupt
dormant quoted values into live injected directives (bsc#1276433).
- CVE-2026-78677: omission of `--separate-git-dir` from `unsafe_git_clone_options` allows for creation of arbitrary git
directories outside the intended clone destination (bsc#1276432).
- CVE-2026-78678: incomplete denylist in the `unsafe_git_revision_options` guard that omits `--contents` and `-S`
options allows for reading of arbitrary files when these options to are passed to `Repo.blame()` (bsc#1276431).
- CVE-2026-78679: positional reference parameter can bypass an unsafe option guard and allows for arbitrary file read
via `TagReference.create()` (bsc#1276430).
- CVE-2026-87817: failure to properly validade the git directory location allows attackers to impersonate the git
directory using tracked files and execute arbitrary code by placing pre-commit hooks in the tracked hooks directory
(bsc#1279905).
- CVE-2026-87818: failure to restrict the `--no-index` option in the high-level diff API allows attackers to read
arbitrary filesystem paths as repository operands and create content-dependent Boolean oracles (bsc#1279906).
- CVE-2026-87819: quadratic backtracking in the `Actor.name_email_regex` regular expression allows attackers to cause
CPU exhaustion and a DoS via a commit with a malformed author field (bsc#1279907).
- GitPython unsafe clone option gate bypass through joined short options (bsc#1273498).

Fixed packages 1

ReleasePackageFixed in
openSUSE · Leap 16.0 python-GitPython 3.1.44-160000.4.1

Vulnerabilities 26

  • Critical 9.8

    GitPython before 3.1.59 Remote Code Execution via Config Injection

    GitPython before 3.1.59 fails to safely re-serialize multi-line git-config values during write operations, corrupting dormant quoted values into injected directives like core.hooksPath. Attackers can craft config files with embedded newlines that become live …

  • High 8.8

    GitPython before 3.1.51 Command Injection via option prefix abbreviation

    GitPython before 3.1.51 contains an incomplete command injection blocklist that fails to account for git's long-option prefix abbreviation feature. Attackers can bypass the unsafe options guard by using abbreviated option names like upload_p instead of upload…

  • High 8.8

    GitPython before 3.1.54 Remote Code Execution via kwarg value smuggling

    GitPython versions before 3.1.54 contain a remote code execution vulnerability in the check_unsafe_options guard that can be bypassed by smuggling git options inside single-character kwarg values. Attackers can supply crafted option dictionaries to clone_from…

  • High 8.8

    GitPython before 3.1.58 Command Execution via split_single_char_options

    GitPython before 3.1.58 contains a command execution vulnerability in the check_unsafe_options guard that can be bypassed by combining a single-character kwarg with split_single_char_options=False. Attackers can supply a crafted kwargs dictionary to guarded m…

  • High 8.8

    GitPython before 3.1.58 Config Injection via option-name

    GitPython before 3.1.58 contains a config-name injection vulnerability in the option-name validator that allows attackers to forge arbitrary git-config directives by injecting equals signs, hash symbols, and whitespace into option names. Attackers can inject …

  • High 8.8

    GitPython before 3.1.60 Remote Code Execution via Git Directory Impersonation

    GitPython before 3.1.60 fails to properly validate the git directory location, allowing attackers to impersonate the git directory using tracked files like gitdir, commondir, and HEAD. Attackers can execute arbitrary code by placing a malicious pre-commit hoo…

  • High 8.4

    GitPython before 3.1.51 Command Injection via unguarded Git options

    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,…

  • High 8.4

    GitPython before 3.1.59 Local File Content Disclosure via .gitmodules

    GitPython before 3.1.59 fails to disable merge_includes when parsing .gitmodules, allowing attackers to disclose local file content by including arbitrary file paths via [include] directives. Attackers can craft a malicious .gitmodules file with include direc…

  • High 8.2

    GitPython before 3.1.58 Path Traversal via .gitmodules Submodule Name

    GitPython before 3.1.58 fails to validate submodule names from .gitmodules files, allowing attackers to create Git repositories at arbitrary filesystem paths outside the intended clone directory. Attackers can craft malicious repositories with traversal seque…

  • High 8.1

    GitPython before 3.1.57 Arbitrary File Overwrite and Read

    GitPython before 3.1.57 fails to guard git option forwarding in IndexFile.checkout() and TagReference.create(), allowing attackers to pass unsafe options via kwargs. Attackers can use --prefix to overwrite arbitrary files with repository content or -F to read…

  • High 8.1

    GitPython before 3.1.54 Arbitrary File Overwrite via diff

    GitPython versions before 3.1.54 contain an arbitrary file overwrite vulnerability in the Diffable.diff method that fails to validate git options passed through kwargs. Attackers can supply the --output argument via the other parameter or output kwarg to writ…

  • High 8.1

    GitPython before 3.1.58 Arbitrary File Overwrite via read-tree

    GitPython versions before 3.1.58 contain an arbitrary file overwrite vulnerability in IndexFile.from_tree, IndexFile.reset, and IndexFile.merge_tree methods that append caller-influenced treeish strings to git read-tree without option validation or argument s…

  • High 7.5

    GitPython before 3.1.52 Environment Variable Exfiltration via clone_from

    GitPython before 3.1.52 is vulnerable to environment-variable exfiltration in Repo.clone_from(). The caller-supplied remote URL is passed through Git.polish_url(), which on non-Cygwin platforms calls os.path.expandvars() on the URL before invoking git clone. …

  • High 7.5

    GitPython before 3.1.55 Environment Variable Exfiltration via Remote.add()

    GitPython before 3.1.55 fails to disable environment variable expansion in Remote.create() and Submodule.add() URL handling, allowing attackers to exfiltrate secrets by supplying URLs containing variable references. Attackers can craft URLs with environment v…

  • High 7.5

    GitPython before 3.1.54 Remote Code Execution via --template

    GitPython before 3.1.54 contains an incomplete denylist in unsafe_git_clone_options that omits --template, allowing attackers to achieve arbitrary command execution during clone operations. Attackers can supply --template pointing to a directory containing ma…

  • High 7.5

    GitPython before 3.1.58 Remote Code Execution via Repo.init

    GitPython before 3.1.58 contains a remote code execution vulnerability in Repo.init that forwards unsafe git options without validation. Attackers can supply a template parameter pointing to a directory with malicious git hooks that execute arbitrary code whe…

  • High 7.5

    GitPython before 3.1.59 Path Traversal via separate-git-dir

    GitPython before 3.1.59 omits --separate-git-dir from unsafe_git_clone_options, allowing attackers to create arbitrary git directories outside the intended clone destination. Attackers can pass a separate_git_dir parameter to Repo.clone_from() or Repo.clone()…

  • High 7.5

    GitPython before 3.1.60 Denial of Service via ReDoS

    GitPython before 3.1.60 contains a regular expression denial of service vulnerability in Actor.name_email_regex that processes commit author and committer fields. Attackers can craft a commit object with a malformed author field containing an unterminated ang…

  • High 7.0

    GitPython before 3.1.50 Newline Injection via config_writer section

    GitPython before 3.1.50 fails to validate newline characters in the section parameter of config_writer(), allowing attackers to inject arbitrary section headers into .git/config. Attackers can inject newlines to create a forged [core] section with hooksPath p…

  • High 7.0

    GitPython before 3.1.53 Config Injection via Submodule Names

    GitPython before 3.1.53 fails to properly escape section names in git config files, allowing attackers to inject arbitrary configuration directives through malicious submodule names. Attackers can inject core.sshCommand or other dangerous config keys into the…

  • Medium 6.5

    GitPython before 3.1.57 Arbitrary File Read via Repo.archive()

    GitPython before 3.1.57 contains an incomplete denylist in the unsafe_git_archive_options guard that omits --add-file and --add-virtual-file options. Attackers can supply these options to Repo.archive() to read arbitrary files from the filesystem and include …

  • Medium 6.5

    GitPython before 3.1.58 Arbitrary File Read via pathspec-from-file

    GitPython versions before 3.1.58 fail to validate options passed to git rm and git checkout commands in IndexFile.remove() and Head.checkout(). Attackers can supply --pathspec-from-file and --pathspec-file-nul parameters to read arbitrary files accessible to …

  • Medium 6.5

    GitPython before 3.1.59 Arbitrary File Read via Repo.blame()

    GitPython versions before 3.1.59 contain an incomplete denylist in the unsafe_git_revision_options guard that omits --contents and -S options, allowing attackers to read arbitrary files by passing these options to Repo.blame(). Attackers can supply revision v…

  • Medium 6.5

    GitPython before 3.1.59 Arbitrary File Read via TagReference.create

    GitPython before 3.1.59 contains an arbitrary file read vulnerability in TagReference.create() where a positional reference parameter bypasses the unsafe option guard. Attackers can supply a reference value like --file=<path> to read arbitrary files, with con…

  • Medium 6.5

    GitPython 3.1.59 Local File Content Oracle via --no-index

    GitPython 3.1.59 fails to restrict the --no-index option in the high-level diff API, allowing attackers to read arbitrary filesystem paths as repository operands. Attackers can combine --no-index with -I/--ignore-matching-lines to create a content-dependent B…

  • Medium 5.4

    GitPython before 3.1.56 Arbitrary File Truncation via Commit.count

    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 …

References

  • report
    https://bugzilla.suse.com/1273357
  • report
    https://bugzilla.suse.com/1273358
  • report
    https://bugzilla.suse.com/1273359
  • report
    https://bugzilla.suse.com/1273364
  • report
    https://bugzilla.suse.com/1273414
  • report
    https://bugzilla.suse.com/1273498
  • report
    https://bugzilla.suse.com/1275745
  • report
    https://bugzilla.suse.com/1275746
  • report
    https://bugzilla.suse.com/1275747
  • report
    https://bugzilla.suse.com/1275748
  • report
    https://bugzilla.suse.com/1275749
  • report
    https://bugzilla.suse.com/1275750
  • report
    https://bugzilla.suse.com/1275751
  • report
    https://bugzilla.suse.com/1275752
  • report
    https://bugzilla.suse.com/1275753
  • report
    https://bugzilla.suse.com/1275754
  • report
    https://bugzilla.suse.com/1275755
  • report
    https://bugzilla.suse.com/1275756
  • report
    https://bugzilla.suse.com/1275757
  • report
    https://bugzilla.suse.com/1276430
  • report
    https://bugzilla.suse.com/1276431
  • report
    https://bugzilla.suse.com/1276432
  • report
    https://bugzilla.suse.com/1276433
  • report
    https://bugzilla.suse.com/1276434
  • report
    https://bugzilla.suse.com/1279905
  • report
    https://bugzilla.suse.com/1279906
  • report
    https://bugzilla.suse.com/1279907
  • web
    https://www.suse.com/security/cve/CVE-2026-67322
  • web
    https://www.suse.com/security/cve/CVE-2026-67323
  • web
    https://www.suse.com/security/cve/CVE-2026-67325
  • web
    https://www.suse.com/security/cve/CVE-2026-67326
  • web
    https://www.suse.com/security/cve/CVE-2026-69097
  • web
    https://www.suse.com/security/cve/CVE-2026-73619
  • web
    https://www.suse.com/security/cve/CVE-2026-73620
  • web
    https://www.suse.com/security/cve/CVE-2026-73621
  • web
    https://www.suse.com/security/cve/CVE-2026-73622
  • web
    https://www.suse.com/security/cve/CVE-2026-73623
  • web
    https://www.suse.com/security/cve/CVE-2026-73624
  • web
    https://www.suse.com/security/cve/CVE-2026-73625