Gitsign is a keyless Sigstore to signing tool for Git commits with your a GitHub / OIDC identity. Prior to 0.16.0, gitsign verify and gitsign verify-tag re-encode commit/tag objects through go-git's EncodeWithoutSignature before checking the signature, instead of verifying against the raw git object bytes. For malformed objects with duplicate tree headers, git-core and go-git parse different trees: git-core uses the first, go-git uses the second. A signature crafted over the go-git-normalized form (second tree) passes gitsign verify while git-core resolves the commit to a completely different tree. This breaks the invariant that a verified signature, the commit semantics git-core presents to users, and the object hash logged in Rekor all refer to the same content. This vulnerability is fixed in 0.16.0.

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

  - Gitsign is a keyless Sigstore to signing tool for Git commits with your a GitHub / OIDC identity. Prior to     0.16.0, gitsign verify and gitsign verify-tag re-encode commit/tag objects through go-git's     EncodeWithoutSignature before checking the signature, instead of verifying against the raw git object     bytes. For malformed objects with duplicate tree headers, git-core and go-git parse different trees: git-     core uses the first, go-git uses the second. A signature crafted over the go-git-normalized form (second     tree) passes gitsign verify while git-core resolves the commit to a completely different tree. This breaks     the invariant that a verified signature, the commit semantics git-core presents to users, and the object     hash logged in Rekor all refer to the same content. This vulnerability is fixed in 0.16.0.
    (CVE-2026-44309)

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

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

  - Gitsign is a keyless Sigstore to signing tool for Git commits with your a GitHub / OIDC identity. Prior to
    0.16.0, gitsign verify and gitsign verify-tag re-encode commit/tag objects through go-git's
    EncodeWithoutSignature before checking the signature, instead of verifying against the raw git object
    bytes. For malformed objects with duplicate tree headers, git-core and go-git parse different trees: git-
    core uses the first, go-git uses the second. A signature crafted over the go-git-normalized form (second
    tree) passes gitsign verify while git-core resolves the commit to a completely different tree. This breaks
    the invariant that a verified signature, the commit semantics git-core presents to users, and the object
    hash logged in Rekor all refer to the same content. This vulnerability is fixed in 0.16.0.
    (CVE-2026-44309)

ID	Name	Product	Family	Type	Severity
315013	Linux Distros Unpatched Vulnerability : CVE-2026-44309	Nessus	Misc.	Local	medium
441592	SCA: security update for github.com/sigstore/gitsign (GHSA-7rmh-48mx-2vwc)	Tenable Cloud Security	SCA Checks	Local	medium
441592	SCA: security update for github.com/sigstore/gitsign (GHSA-7rmh-48mx-2vwc)	Tenable Self-Hosted Container Security	SCA Checks	Local	medium

Detections

Analytics

CVE-2026-44309

medium

Tenable Plugins

medium

medium

medium