CVE-2026-49834: sigstore-go has a multi-log threshold bypass via single compromised log
(updated )
What kind of vulnerability is it? Who is impacted?
A verifier configured with WithTransparencyLog(N>1) or WithSignedCertificateTimestamps(N>1) expected defense-in-depth against the compromise of a single log instance. However, threshold counting counted verified witnesses per-entry or per-validation-path rather than per-log-authority.
As a result, a single compromised transparency log could forge multiple entries with different indices, and a single compromised CT log could verify multiple times (either across multiple certificate chains or via multiple embedded SCTs), fully satisfying the multi-log threshold requirements and defeating the multi-log policy.
Note that this does not affect Cosign, as Cosign sets a threshold of 1.
References
- github.com/advisories/GHSA-9vcr-p3rj-q5q6
- github.com/sigstore/sigstore-go/commit/dbb07e62623edd5b175fb9dd5a41dcb85a159207
- github.com/sigstore/sigstore-go/pull/633
- github.com/sigstore/sigstore-go/releases/tag/v1.2.0
- github.com/sigstore/sigstore-go/security/advisories/GHSA-9vcr-p3rj-q5q6
- nvd.nist.gov/vuln/detail/CVE-2026-49834
Code Behaviors & Features
Detect and mitigate CVE-2026-49834 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Dependency Scanning using SBOM also detects vulnerabilities from proprietary advisories that this site does not include. Learn more about Dependency Scanning using SBOM →