sigstore-go is a Go library for Sigstore signing and verification. Prior to 1.2.0, a verifier configured with WithTransparencyLog(N>1) or WithSignedCertificateTimestamps(N>1) counts verified witnesses per entry or per validation path rather than per log authority, allowing a single compromised transparency log or CT log to satisfy multi-log threshold requirements and defeat the multi-log policy. This issue is fixed in version 1.2.0.
Fix
Patch, vendor advisory and mitigation references on NVD 3
- https://github.com/sigstore/sigstore-go/commit/dbb07e62623edd5b175fb9dd5a41dcb85a159207 Patch
- https://github.com/sigstore/sigstore-go/pull/633 Issue Tracking, Patch
- https://github.com/sigstore/sigstore-go/security/advisories/GHSA-9vcr-p3rj-q5q6 Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 7.5 · sigstoreNVD modified 2026-10-24 20:10
Affected (CPE criteria) 1
cpe:2.3:a:sigstore:sigstore-go:*:*:*:*:*:*:*:*
References 4
- https://github.com/sigstore/sigstore-go/commit/dbb07e62623edd5b175fb9dd5a41dcb85a159207 Patch
- https://github.com/sigstore/sigstore-go/pull/633 Issue Tracking, Patch
- https://github.com/sigstore/sigstore-go/releases/tag/v1.2.0 Product, Release Notes
- https://github.com/sigstore/sigstore-go/security/advisories/GHSA-9vcr-p3rj-q5q6 Vendor Advisory