CVE-2026-44310
- Source
- https://cve.org/CVERecord?id=CVE-2026-44310
- Import Source
- https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-44310.json
- JSON Data
- https://api.osv.dev/v1/vulns/CVE-2026-44310
- Aliases
- Downstream
- Related
- Published
- 2026-05-15T16:17:53.558Z
- Modified
- 2026-08-04T11:50:58.886125098Z
- Severity
-
- 5.4 (Medium) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L CVSS Calculator
- Summary
- gitsign --verify panics on empty-certificate PKCS7 and exits 0, bypassing exit-code callers
- Details
-
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.
- Database specific
{ "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/44xxx/CVE-2026-44310.json", "cna_assigner": "GitHub_M", "cwe_ids": [ "CWE-129", "CWE-390" ] }- References