Bug 2501871 (CVE-2026-49834) - CVE-2026-49834 github.com/sigstore/sigstore-go: sigstore-go: Security Policy Bypass via Compromised Log
Summary: CVE-2026-49834 github.com/sigstore/sigstore-go: sigstore-go: Security Policy ...
Keywords:
Status: NEW
Alias: CVE-2026-49834
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 2513977 2513981 2513984 2513978 2513979 2513980 2513982 2513983
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-07-17 20:01 UTC by OSIDB Bzimport
Modified: 2026-09-10 14:19 UTC (History)
19 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:

Attachments (Terms of Use)

Description OSIDB Bzimport 2026-07-17 20:01:33 UTC 
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.
Note You need to log in before you can comment on or make changes to this bug.