CVE-2026-44309

MEDIUM

gitsign verify accepts signatures over go-git-normalized bytes, enabling trust confusion on malformed commits

Title source: cna
STIX 2.1

Description

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.

References (1)

Core 1
Core References

Scores

CVSS v3 5.3
EPSS 0.0001
EPSS Percentile 2.1%
Attack Vector NETWORK
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N

CISA SSVC

Vulnrichment
Exploitation poc
Automatable no
Technical Impact partial

Details

CWE
CWE-295 CWE-347
Status published
Products (2)
sigstore/gitsign 0 - 0.16.0Go
sigstore/gitsign < 0.16.0
Published May 15, 2026
Tracked Since May 15, 2026