Vulnerability in github.com/sigstore/gitsign (CVE-2026-44310)
Summary
Vulnerability in github.com/sigstore/gitsign (CVE-2026-44310). Risk of unauthorized operations or information disclosure. Exploitable via nil. Mitigation: upgrade to 0.15.0 or later.
Original description
The description as published by the source.
Summary
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.
Severity
Medium (CVSS 3.1: 5.8)
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
- Attack Vector: Network — attacker pushes a commit carrying a crafted signature to any accessible repository, or delivers the signature file out-of-band
- Attack Complexity: Low — stripping certificates from a PKCS7 object requires only standard ASN.1 tooling
- Privileges Required: None — writing to an accessible repo (or creating a repo a victim clones) is sufficient
- User Interaction: Required — victim must run
git verify-commit,gitsign --verify, or an equivalent verification step - Scope: Unchanged
- Confidentiality Impact: None
- Integrity Impact: Low — exit-code-only callers (scripts, some CI pipelines) treat the panicked verification as success; git's ow…
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-44310 has been found in github.com/sigstore/gitsign.
Attackers can target a specific entry point like nil over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.4/10.
What to do: upgrade github.com/sigstore/gitsign to 0.15.0 or later.
If unsure, ask your IT team or search "github.com/sigstore/gitsign CVE-2026-44310" on the vendor's site.
CVE-2026-44310 (github.com/sigstore/gitsign) — CWE-129 / CVSS v3 5.4
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: nil / main.go / GOODSIG / certificates
Patched: 0.15.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-129) exists in github.com/sigstore/gitsign. Attackers reach the vulnerable code path via nil without authentication.
Check the vendor advisory for the affected versions of github.com/sigstore/gitsign. Attack surface: nil / main.go / GOODSIG / certificates.
Severity: Medium (CVSS 5.4/10). Risk of unauthorized operations or information disclosure.
Update to 0.15.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/sigstore/gitsign' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/sigstore/gitsign' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/sigstore/gitsignを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/sigstore/gitsign to 0.15.0ステージング環境で 0.15.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-44310 gitsign
- Ubuntu UBUNTU-CVE-2026-44310 gitsign
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com