CVE-2026-49834

mediumCVSS 5.9covered by 1 sourcefirst seen 2026-07-09

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.

⚡ Watch CVE-2026-49834

Get an email if CVE-2026-49834 is added to CISA KEV, gains public exploit code, or a new advisory cites it — max one per day, one-click unsubscribe.

Advisory coverage (1)

mediumGHSA-9vcr-p3rj-q5q6: sigstore-go has a multi-log threshold bypass via single compromised logghsa · 2026-07-09

External references

NVD record for CVE-2026-49834

CVE.org record

Embed the live status

— this badge updates automatically when the KEV or exploit status changes. How to embed it →

[![CVE-2026-49834 status](https://www.csirts.com/badge/CVE-2026-49834)](https://www.csirts.com/cve/CVE-2026-49834)