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
Configurations
No configuration.
History
15 May 2026, 18:16
| Type | Values Removed | Values Added |
|---|---|---|
| References | () https://github.com/sigstore/gitsign/security/advisories/GHSA-7rmh-48mx-2vwc - |
15 May 2026, 17:16
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Information
Published : 2026-05-15 17:16
Updated : 2026-05-18 19:36
NVD link : CVE-2026-44309
Mitre link : CVE-2026-44309
CVE.ORG link : CVE-2026-44309
JSON object : View
Products Affected
No product.