The remote host is affected by the vulnerability described in GLSA-202611-02 (git: Multiple Vulnerabilities)

    Multiple vulnerabilities have been discovered in git. Please review the CVE identifiers referenced below     for details.

Tenable has extracted the preceding description block directly from the Gentoo Linux 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 AlmaLinux 9.2 host has packages installed that are affected by multiple vulnerabilities as referenced in the TuxCare ALMALINUX9.2:CLSA-2026:1794512753 advisory.

  - Arbitrary data can be read or written through git-fast-import(1) and git-fast-export(1) features not     marked unsafe (CVE-2026-114466)

  - Affected versions of Git have a heap buffer overflow in the three-way merge code (xdiff), which an     attacker can trigger through a repository they control. When Git merges a file, it first adds up the size     of the merged output, allocates a buffer of that size, and then writes the output into it. That total was     kept in a 32-bit signed integer. The conflict-marker-size attribute, which can be set from a committed     .gitattributes file, accepts any positive integer, and the markers are written several times for every     conflict. A small file with a huge marker size and many separate conflicts can therefore push the total     past 4 GiB, so the integer wraps to a small value and Git writes attacker-controlled merge output past the     end of a buffer that is too small. At minimum this crashes Git, and because the overflow is large and its     contents are largely attacker-controlled, worse heap corruption is possible. Any command that does a     textual three-way merge can trigger it, such as git-merge(1), git-rebase(1), git-cherry-pick(1), and git-     merge-tree(1). The latter is most likely a target for Git forges, which might use git-merge-tree(1) on the     server-side to check mergeability. When the server reads attributes from trees in the repository (for     example through attr.tree or --attr-source), any user who can push branches and request that they be     merged (for example by opening a pull or merge request) can trigger the overflow without anyone else doing     anything, and the data they push is small because the oversized output only appears during the merge. The     problem has been patched by computing the size as size_t and checking every addition for overflow, so Git     stops with an error instead of overflowing. Servers that cannot upgrade right away can add * conflict-     marker-size=7 to each repository's info/attributes as a workaround, which overrides any in-tree     .gitattributes, or turn off server-side mergeability checks for untrusted repositories. (CVE-2026-105437)

  -  Please review the referenced CVE identifiers for details.  (CVE-2026-111760)

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.

  -  Please review the referenced CVE identifiers for details.  (CVE-2026-114466)

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

The version of FreeBSD installed on the remote host is prior to tested version. It is, therefore, affected by multiple vulnerabilities as referenced in the 24e1443d-dd3b-11f1-b094-bc2411e144f8 advisory.

    Git development team reports:
    CVE-2026-111760:
                Recursive clones are susceptible to Remote Code Execution: an                 attacker-controlled repository can be crafted in a way that                 exploits a bug in Git whereby Git can be fooled into overwriting                 a gitfile (used for submodules) with a symbolic link that then                 points to a directory with malicious config or hooks. The config                 or hooks may have attacker-specified code.

    CVE-2026-113408:
                It is possible for a server to advertise an unborn HEAD that                 contains path-traversal characters (e.g.,                 `refs/heads/../../../TARGET`). With the files ref backend that                 can lead to ref-updating actions to write to unwanted files.

    CVE-2026-114466:
                In response to CVE-2019-1348, `fast-import` disallows the                 `export-marks` feature by default. The features                 `rewrite-submodules-to` and `rewrite-submodules-from` as well as                 the option `export-pack-edges` that were introduced in the                 meantime also allow reading from arbitrary paths, and are                 therefore now also disallowed by default.

    CVE-2026-114467:
                When Git strips the GPG signatures from a commit message, it only                 accounts for two signatures. A commit message containing more                 than two signatures therefore causes a stack memory corruption.
                This can be triggered when using `git merge` with a tag which                 contains more than two signatures, making way for a DoS attack                 which can potentially also affect forges.

    CVE-2026-114469:
                Git rejects patches larger than ~1 GiB, but that check only                 considered the size of the patch as it appears in the input,                 which for binary patches is much smaller than the size of the                 file the patch describes. A binary patch that inflates to a very                 large size therefore slipped past the check and crashed Git with                 an out-of-bounds read.

    CVE-2026-105437:
                When merging, Git computes the size of the buffer holding the                 merge result in a way that can overflow for very large merges,                 which can be triggered by a large number of conflicts combined                 with a large `conflict-marker-size`. The resulting buffer can                 then be too small, and Git writes past its end (and, before and                 after that, before its start), corrupting the heap.


Tenable has extracted the preceding description block directly from the FreeBSD 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 version of git installed on the remote host is prior to 2.47.3-1. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2-2026-4109 advisory.

    Size calculations for very large merge results can overflow, leading to an undersized buffer and heap     corruption. (CVE-2026-105437)

    Recursive clones can lead to remote code execution through unsafe handling of submodule-related repository     metadata. (CVE-2026-111760)

    A server can advertise a malformed unborn HEAD, causing unintended file writes during subsequent ref     updates with the files ref backend. (CVE-2026-113408)

    Certain fast-import features can access arbitrary paths and are now disallowed by default.
    (CVE-2026-114466)

    Removing more than two GPG signatures from commit messages can corrupt stack memory, potentially causing     denial of service during merges. (CVE-2026-114467)

    Binary-patch size validation can be bypassed because it checks the encoded input rather than the inflated     result, potentially causing an out-of-bounds read and crash. (CVE-2026-114469)

Tenable has extracted the preceding description block directly from the tested product 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 version of git installed on the remote host is prior to 2.50.2 / 2.56.1. It is, therefore, affected by multiple vulnerabilities as referenced in the SSA:2026-315-02 advisory.

    New git packages are available for Slackware 15.0 and -current to fix security issues.

Tenable has extracted the preceding description block directly from the git 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	名前	製品	ファミリー	公開日	更新日	深刻度
378752	GLSA-202611-02 : git: Multiple Vulnerabilities	Nessus	Gentoo Local Security Checks	2026/11/11	2026/11/12	high
379790	AlmaLinux 9.2 [TuxCare] Security Update: git / git-all / git-core / git-core-doc / git-credential-libsecret / etc Multiple Vulnerabilities (ALMALINUX9.2:CLSA-2026:1794512753)	Nessus	Alma Linux Local Security Checks	2026/11/12	2026/11/12	high
378548	Linux Distros Unpatched Vulnerability : CVE-2026-114466	Nessus	Misc.	2026/11/10	2026/11/11	critical
378782	FreeBSD : git -- multiple vulnerabilities (24e1443d-dd3b-11f1-b094-bc2411e144f8)	Nessus	FreeBSD Local Security Checks	2026/11/11	2026/11/12	high
379820	Amazon Linux 2 : git (ALAS-2026-4109)	Nessus	Amazon Linux Local Security Checks	2026/11/12	2026/11/12	high
379266	Slackware Linux 15.0 / current git Multiple Vulnerabilities (SSA:2026-315-02)	Nessus	Slackware Local Security Checks	2026/11/11	2026/11/11	high

検出

プラグインの検索

high

high

critical

high

high

high