Vulnerability Description
Gitsign is a keyless Sigstore to signing tool for Git commits with your a GitHub / OIDC identity. From 0.4.0 to before 0.15.0, CertVerifier.Verify() in pkg/git/verifier.go unconditionally dereferences certs[0] after sd.GetCertificates() without checking the slice length. A CMS/PKCS7 signed message with an empty certificate set is a structurally valid DER payload; GetCertificates() returns an empty slice with no error, causing an immediate index-out-of-range panic. On the gitsign --verify code path (the GPG-compatible mode invoked by git verify-commit), the panic is silently recovered by internal/io/streams.go's Wrap() function, which returns nil instead of an error. main.go then exits with code 0, causing exit-code-only verification callers to interpret the failed verification as success. This vulnerability is fixed in 0.15.0.
CVSS Score
MEDIUM
Related Weaknesses (CWE)
References
- https://github.com/sigstore/gitsign/security/advisories/GHSA-7c37-gx6w-8vc5
- https://github.com/sigstore/gitsign/security/advisories/GHSA-7c37-gx6w-8vc5
FAQ
What is CVE-2026-44310?
CVE-2026-44310 is a vulnerability with a CVSS score of 5.4 (MEDIUM). Gitsign is a keyless Sigstore to signing tool for Git commits with your a GitHub / OIDC identity. From 0.4.0 to before 0.15.0, CertVerifier.Verify() in pkg/git/verifier.go unconditionally dereferences...
How severe is CVE-2026-44310?
CVE-2026-44310 has been rated MEDIUM with a CVSS base score of 5.4/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-44310?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.