# CVE-2026-44310

## Summary

- **CVE ID:** CVE-2026-44310
- **Severity:** MEDIUM
- **CVSS Score:** 5.4 (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L)
- **CWE:** CWE-129, CWE-390
- **Published:** May 15, 2026
- **Last Modified:** May 15, 2026

## 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.

## Affected Products

- sigstore — gitsign (>= 0.4.0, < 0.15.0)

## References

- [CNA](https://github.com/sigstore/gitsign/security/advisories/GHSA-7c37-gx6w-8vc5)

## Exploitation Prediction (EPSS)

- **EPSS Score:** 0.11%
- **EPSS Percentile:** 1.5

---
_Exported from OnDuty AI Vulnerability Intelligence on 2026-09-11._