https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Thu, 01 Oct 2026 03:00:50 +0000 https://vulnerability.circl.lu/vuln/ghsa-9vcr-p3rj-q5q6 <p><strong>Affected:</strong> Go: github.com/sigstore/sigstore-go</p> <p>### Impact _What kind of vulnerability is it? Who is impacted?_</p> <p>A verifier configured with WithTransparencyLog(N&gt;1) or WithSignedCertificateTimestamps(N&gt;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.</p> <p>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.</p> <p>Note that this does not affect Cosign, as Cosign sets a threshold of 1.</p> <p>### Patches _Has the problem been patched? What versions should users upgrade to?_</p> <p>Upgrade to v1.1.5.</p> <p>### Workarounds _Is there a way for users to fix or remediate the vulnerability without upgrading?_</p> <p>There is no workaround, beyond relying on trusted logs.</p> <p><strong>Affected:</strong> Go: github.com/sigstore/sigstore-go</p> <p>### Impact _What kind of vulnerability is it? Who is impacted?_</p> <p>A verifier configured with WithTransparencyLog(N&gt;1) or WithSignedCertificateTimestamps(N&gt;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.</p> <p>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.</p> <p>Note that this does not affect Cosign, as Cosign sets a threshold of 1.</p> <p>### Patches _Has the problem been patched? What versions should users upgrade to?_</p> <p>Upgrade to v1.1.5.</p> <p>### Workarounds _Is there a way for users to fix or remediate the vulnerability without upgrading?_</p> <p>There is no workaround, beyond relying on trusted logs.</p> https://vulnerability.circl.lu/vuln/ghsa-9vcr-p3rj-q5q6