Medium severity · published May 15, 2026
CVE-2026-44309
gitsign verify accepts signatures over go-git-normalized bytes, enabling trust confusion on malformed commits
5.3
CVSS
0.1%
EPSS
No
On KEV
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.
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N
Attack vector
Network
Complexity
High
Privileges
None
User interaction
Required
Confidentiality
None
Integrity
High
Availability
None
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)0.1% · higher than 3% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
GI
gitsign · sigstore
< 0.16.0 · source: vendor
Affected product
GI
gitsign
sigstore
More from gitsign
5.4
CVE-2026-44310
gitsign --verify panics on empty-certificate PKCS7 and exits 0, bypassing exit-code callers
5.3
CVE-2023-47122
Gitsign is software for keyless Git signing using Sigstore