Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Versions of gitsign before 0.16.0 verify re-encoded commit data instead of raw bytes, so malformed commits with duplicate tree headers can pass. An attacker who shares such a commit through a git remote can get a victim running gitsign verify to accept a signature over content that git resolves differently. Upgrade to gitsign 0.16.0.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 5.3 | Medium | 3.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0014, the 3rd percentile, on 12 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:14 UTC First seen by agentprime
- 31 Oct 2026, 14:14 UTC Confirmed by OSV