CVE 5.4 MEDIUM

gitsign –verify panics on empty-certificate PKCS7 and exits 0, bypassing exit-code callers_CVE-2026-44310

5.4 / 10
MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L

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.

Basic Information

ID CVE-2026-44310
Source GitHub_M
Published May 15, 2026 at 16:17
Modified May 15, 2026 at 16:44

Affected Product

Vendor sigstore
Product gitsign
Version >= 0.4.0, < 0.15.0
Affected Versions sigstore gitsign >= 0.4.0, < 0.15.0

CWE Classification

References

💭 Join the Security Discussion

🔒 Your email address will not be published. Required fields are marked *

⚠️ Please be respectful and constructive in your comments. Security discussions should remain professional.