gitsign
Affected
- introduced
0(ecosystem)
Fixed versions
None listed
Fix
No fixed version is listed.
Advisory
Also known as: CVE-2026-44309
The record has no summary.
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.
Medium Basis: CVSS v3 score 5.3, vector CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N
0 (ecosystem)None listed
No fixed version is listed.
0, fixed 0.16.0-1 (ecosystem)0.16.0-1
0.16.0-1sudo apt-get update && sudo apt-get upgradeThis command upgrades the distribution's packages. Compare the fixed version with the version you have installed.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: Debian Security Tracker (converted by OSV.dev)
Debian Security Tracker, converted to OSV by OSV.dev.