Read the docs
TI-2024-34651 Aliases CVE-2024-51746GHSA-8pmp-678w-c8xx

Use of incorrect Rekor entries during verification in gitsign

Priority MEDIUM 43CWE-706Published · Updated

Key facts

Attack vector
Local
Privileges required
None
User interaction
Active
Attack complexity
High
Attack requirements
Present
Impact type
Security bypass
Confidentiality · integrity · availability
None · Low · None
Fix status
Partial Red Hat: 1 without a fix

Attack profile from CVSS 4.0 · CNA. Fix status from CNA, GitHub and Red Hat. Impact type from CWE-287.

Summary

Gitsign is a keyless Sigstore to signing tool for Git commits with your a GitHub / OIDC identity. gitsign may select the wrong Rekor entry to use during online verification when multiple entries are returned by the log. gitsign uses Rekor's search API to fetch entries that apply to a signature being verified. The parameters used for the search are the public key and the payload. The search API returns entries that match either condition rather than both. When gitsign's credential cache is used, there can be multiple entries that use the same ephemeral keypair / signing certificate. As gitsign assumes both conditions are matched by Rekor, there is no additional validation that the entry's hash matches the payload being verified, meaning that the wrong entry can be used to successfully pass verification. Impact is minimal as while gitsign does not match the payload against the entry, it does ensure that the certificate matches. This would need to be exploited during the certificate validity window (10 minutes) by the key holder.

Why it matters now

Exploitation Proof of concept CISA SSVC · not in CISA KEV
EPSS 0.00116 1st percentileScored 2026-11-07
Fix Partial gitsign (sigstore): 0.11.0github.com/sigstore/gitsign (Go): 0.11.0Red Hat: 1 without a fix

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
Poc
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
sigstoregitsignbefore 0.11.00.11.0Patch availableCNA
—github.com/sigstore/gitsign (Go)before 0.11.00.11.0Patch availableGHSA-8pmp-678w-c8xx
  • gitsign Vendorsigstore Affected before 0.11.0 Fixed in 0.11.0 Patch available CNA
  • github.com/sigstore/gitsign (Go) Vendor— Affected before 0.11.0 Fixed in 0.11.0 Patch available GHSA-8pmp-678w-c8xx

CPE names CISA-ADP · 1

CPEVersionsRoleVendor
cpe:2.3:a:sigstore:gitsign:*:*:*:*:*:go:*:*——sigstore
  • cpe:2.3:a:sigstore:gitsign:*:*:*:*:*:go:*:* Versions — — ·sigstore

Remediation

  • Fix · CNA gitsign (sigstore) Fixed in 0.11.0
  • Fix · GHSA-8pmp-678w-c8xx github.com/sigstore/gitsign (Go) Fixed in 0.11.0 Advisory →

Vendor assessments

Red Hat

Red Hat rating: Low. Red Hat's page for this CVE →

ProductStatusPlan or fix
Red Hat Trusted Artifact SignerAffectedNo fix yet: Fix deferred

Timeline

  1. 2026-10-02 Threatist record created from CVE-2024-51746
  2. 2026-10-03 Alias added: GHSA-8pmp-678w-c8xx

References

Advisory 1

Other 2

  • TI-2022-16356 False positive signature verification in cosign CVSS 3.1CRITICAL 9.8
  • TI-2026-36084 sigstore-js: `certificateOIDs` verification constraints are silently dropped and never enforced CVSS 3.1HIGH 7.5
  • TI-2024-19670 Cosign vulnerable to machine-wide denial of service via malicious artifacts CVSS 3.1HIGH 7.5
  • TI-2026-18290 Fulcio vulnerable to Server-Side Request Forgery (SSRF) via MetaIssuer Regex Bypass CVSS 3.1MEDIUM 5.8
  • TI-2026-36085 sigstore-js: Insufficient Verification of Data Authenticity CVSS 3.1MEDIUM 6.5
  • TI-2024-19669 Cosign vulnerable to system-wide denial of service via malicious attachments CVSS 3.1MEDIUM 5.9
See all 39 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences