github.com/sigstore/sigstore-go
Affected
- introduced
0, fixed1.2.0(semver)
Fixed versions
1.2.0
Fix
- Fixed version
1.2.0go get github.com/sigstore/[email protected]
Advisory
Also known as: CVE-2026-49834, GO-2026-5952
sigstore-go has a multi-log threshold bypass via single compromised log
Impact
_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.
Patches
_Has the problem been patched? What versions should users upgrade to?_
Upgrade to v1.1.5.
Workarounds
_Is there a way for users to fix or remediate the vulnerability without upgrading?_
There is no workaround, beyond relying on trusted logs.
Medium Basis: The source's own band: MODERATE
0, fixed 1.2.0 (semver)1.2.0
1.2.0go get github.com/sigstore/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0