There are packages installed that are affected by a vulnerability referenced in the following CVE:

  - 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). (CVE-2026-73621)

The remote SUSE Linux SLED15 / SLED_SAP15 / SLES15 / SLES_SAP15 host has a package installed that is affected by multiple vulnerabilities as referenced in the SUSE-SU-2026:4072-1 advisory.

    - CVE-2026-42215: command injection via Git options bypass (bsc#1264604).
    - CVE-2026-42284: unsafe option check validates multi_options before shlex.split transforms it     (bsc#1264605).
    - CVE-2026-44243: path traversal in GitPython reference APIs allows arbitrary file write and delete     outside the       repository (bsc#1264606).
    - CVE-2026-44244: newline injection in config_writer().set_value() enables RCE via core.hooksPath     (bsc#1264608).
    - CVE-2026-67322: vulnerable to environment-variable exfiltration in Repo.clone_from() (bsc#1273357).
    - CVE-2026-67323: fails to guard against dangerous Git options passed as keyword arguments in     Repo.archive() and       git.ls_remote() (bsc#1273358).
    - CVE-2026-67325: contains an incomplete command injection blocklist that fails to account for git's long-     option prefix       abbreviation feature (bsc#1273359).
    - CVE-2026-67326: fails to validate newline characters in the section parameter of config_writer()     (bsc#1273364).
    - CVE-2026-69097: fails to properly escape section names in git config files, allowing attackers to inject     arbitrary       configuration directives through malicious submodule names (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: fails to disable merge_includes when parsing .gitmodules, allowing attackers to disclose     local file       content by including arbitrary file paths via [include] directives (bsc#1276434).
    - CVE-2026-78676: fails to safely re-serialize multi-line git-config values during write operations,     corrupting dormant       quoted values into injected directives (bsc#1276433).
    - CVE-2026-78677: allowing creation of arbitrary git directories outside the intended clone destination     (bsc#1276432).
    - CVE-2026-78678: an incomplete denylist in the unsafe_git_revision_options guard that omits --contents     and -S options,       allowing attackers to read arbitrary files (bsc#1276431).
    - CVE-2026-78679: an arbitrary file read vulnerability in TagReference.create() (bsc#1276430).

Tenable has extracted the preceding description block directly from the SUSE security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - 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). (CVE-2026-73621)

Note that Nessus relies on the presence of the package as reported by the vendor.

The remote Debian 12 host has packages installed that are affected by multiple vulnerabilities as referenced in the dla-4872 advisory.

    -------------------------------------------------------------------------     Debian LTS Advisory DLA-4872-1                debian-lts@lists.debian.org     https://www.debian.org/lts/security/                       Emmanuel Arias     October 31, 2026                              https://wiki.debian.org/LTS
    -------------------------------------------------------------------------

    Package        : python-git     Version        : 3.1.30-1+deb12u3     CVE ID         : CVE-2026-42215 CVE-2026-42284 CVE-2026-44243 CVE-2026-44244                      CVE-2026-67322 CVE-2026-67323 CVE-2026-67324 CVE-2026-67325                      CVE-2026-67326 CVE-2026-69097 CVE-2026-73619 CVE-2026-73620                      CVE-2026-73621 CVE-2026-73622 CVE-2026-73623 CVE-2026-73624                      CVE-2026-73625 CVE-2026-76217 CVE-2026-76218 CVE-2026-76219                      CVE-2026-76220 CVE-2026-76221 CVE-2026-76222 CVE-2026-78675                      CVE-2026-78676 CVE-2026-78677 CVE-2026-78678 CVE-2026-78679                      CVE-2026-87817 CVE-2026-87818 CVE-2026-87819 CVE-2026-100689                      CVE-2026-110855 CVE-2026-110856 CVE-2026-110857 CVE-2026-110858                      CVE-2026-110859 CVE-2026-110860 CVE-2026-114145     Debian Bug     : 1135349 1135350 1143454 1143602 1144344 1144929

    Multiple security vulnerabilities were discovered in python-git     (GitPython), a Python library used to interact with git repositories.
    These issues could result in arbitrary command execution, path traversal     with arbitrary file read or write, git config injection, leaking of     secrets through environment variable expansion or denial of service     (ReDoS).

    CVE-2026-42215

        Unsafe options passed as underscored keyword arguments were not         blocked, which could lead to command execution.

    CVE-2026-42284

        Unsafe options were not checked after splitting multi_options with         shlex, which could lead to command execution.

    CVE-2026-44243

        When manipulating references, access to files outside the repository         was not prevented, allowing arbitrary file access.

    CVE-2026-44244

        The config writer did not reject control characters in config values,         allowing config injection.

    CVE-2026-67322

        Environment variables were expanded in clone URLs, which could leak         secrets to a remote host.

    CVE-2026-67323

        Unsafe options (--exec, --upload-pack, ...) were not guarded in the         archive, fetch, pull, push, ls-remote, blame and revision APIs, which         could lead to command execution.

    CVE-2026-67324

        Abbreviated long options bypassed the unsafe option checks, leading to         command execution.

    CVE-2026-67325

        Joined short options bypassed the unsafe option checks, leading to         command execution.

    CVE-2026-67326

        Config section names were not validated before writing, allowing         config injection.

    CVE-2026-69097

        Config section names containing an unquoted closing bracket could         inject arbitrary settings into .git/config.

    CVE-2026-73619

        The --add-file, --add-virtual-file (archive) and --bundle-uri (clone)         options were missing from the unsafe option lists, which could lead to         command execution or arbitrary file access.

    CVE-2026-73620

        Unsafe options in IndexFile.checkout() (--prefix) and         TagReference.create() (-F/--file) were not blocked, which could write         to or read from arbitrary filesystem paths.

    CVE-2026-73621

        Unsafe output options were not rejected in Commit.count, which could         write to arbitrary filesystem paths.

    CVE-2026-73622

        Environment variables were expanded in remote and submodule URLs,         which could leak secrets to a remote host.

    CVE-2026-73623

        The unsafe --template option was not rejected when cloning, which         could read from arbitrary filesystem paths.

    CVE-2026-73624

        Unsafe output options were not guarded in diff operations, which could         write to arbitrary filesystem paths.

    CVE-2026-73625

        The values of split short options were not validated, which could         bypass the unsafe option checks in clone, remote, revision, blame and         archive operations.

    CVE-2026-76217

        The --pathspec-from-file options were not guarded in IndexFile.remove,         Head.checkout and HEAD.reset, which could read from arbitrary         filesystem paths.

    CVE-2026-76218

        Unsafe git init options (--template, --separate-git-dir) were not         guarded in Repo.init, which could read from or write to arbitrary         filesystem paths.

    CVE-2026-76219

        The --index-output option was not guarded in read-tree calls made by         from_tree, merge_tree and reset, which could write to an arbitrary         path.

    CVE-2026-76220

        The value joined to one-character options was not checked when         split_single_char_options is false, which could bypass the unsafe         option checks.

    CVE-2026-76221

        Config option names containing characters that could inject arbitrary         settings when writing the config were not rejected.

    CVE-2026-76222

        Submodule names read from .gitmodules were not validated before         filesystem operations, allowing path traversal outside the repository.

    CVE-2026-78675

        Include directives in .gitmodules were processed, which could read         arbitrary files.

    CVE-2026-78676

        Multiline config values were not preserved when writing, which could         inject new options into the config.

    CVE-2026-78677

        The --separate-git-dir option was not blocked in Repo.clone() and         Repo.clone_from(), which could write repository metadata to an         arbitrary path.

    CVE-2026-78678, CVE-2026-78679

        File-reading options were not blocked in blame, diff and tag APIs,         which could read arbitrary files.

    CVE-2026-87817

        Repository discovery did not prefer the .git entry nor validate         candidate git directories, diverging from git's behaviour.

    CVE-2026-87818

        The --no-index option was not treated as an unsafe diff option, which         allowed diffing arbitrary filesystem paths.

    CVE-2026-87819

        Actor identities were parsed with regular expressions, allowing         quadratic backtracking (ReDoS) on malformed identities.

    CVE-2026-100689

        Submodule checkout paths that resolve outside the repository or         through a symbolic link were not rejected in Submodule.update, unlike         in add and move.

    CVE-2026-110855

        Environment variables were expanded in the separate_git_dir path when         cloning, so repository metadata could be written to an unexpected         location.

    CVE-2026-110856

        Actor identities and dates in commit authors, committers and taggers         were parsed with backtracking regular expressions, allowing excessive         CPU use (ReDoS) on malformed metadata.

    CVE-2026-110857

        The unsafe option and protocol checks were incomplete in         Git.ls_remote(), Repo.merge_base() and IndexFile.move(), which omitted         guards already used by sibling APIs.

    CVE-2026-110858

        Option-shaped remote names were not rejected in Remote.update(), which         git forwards to fetch --multiple without an option terminator,         allowing a leading-dash name to change the requested operation.

    CVE-2026-110859

        The positional reference passed by Head.checkout() was not validated         against the unsafe-option policy, so reference names originating in a         cloned repository could bypass it.

    CVE-2026-110860

        Submodule checkout, move and metadata paths that traverse intermediate         symbolic links were not rejected before performing filesystem         operations.

    CVE-2026-114145

        GitPython validated a submodule's '.git' path only after cloning into         it, which could lead to remote code execution.

    For Debian 12 bookworm, these problems have been fixed in version     3.1.30-1+deb12u3.

    We recommend that you upgrade your python-git packages.

    For the detailed security status of python-git please refer to     its security tracker page at:
    https://security-tracker.debian.org/tracker/python-git

    Further information about Debian LTS security advisories, how to apply     these updates to your system and frequently asked questions can be     found at: https://wiki.debian.org/LTS     Attachment:
    signature.asc     Description: PGP signature

Tenable has extracted the preceding description block directly from the Debian security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

ID	Name	Product	Family	Published	Updated	Severity
474832	Echo: python-git: security update to 3.1.56	Tenable Cloud Security	Echo Local Security Checks	10/16/2026	10/16/2026	medium
474832	Echo: python-git: security update to 3.1.56	Tenable Self-Hosted Container Security	Echo Local Security Checks	10/16/2026	10/16/2026	medium
348443	SUSE SLED15 / SLES15 Security Update : python-GitPython (SUSE-SU-2026:4072-1)	Nessus	SuSE Local Security Checks	9/21/2026	9/21/2026	critical
335369	Linux Distros Unpatched Vulnerability : CVE-2026-73621	Nessus	Misc.	8/14/2026	11/3/2026	medium
374599	Debian dla-4872 : python-git-doc - security update	Nessus	Debian Local Security Checks	10/31/2026	10/31/2026	critical

Detections

Analytics

Plugins Search

medium

medium

critical

medium

critical