Trust-policy bypass via duplicate log witness counting
Published Jul 17, 2026 · Updated Jul 17, 2026
Cryptographic verification bypass in Sigstore sigstore-go before 1.2.0 allows remote attackers to defeat multi-log trust policies. VerifySignedCertificateTimestamp and VerifyTlogEntry count repeated SCT paths or entries without deduplicating the originating log authority. Exploitation requires a threshold above one and control of one trusted transparency or CT log; accepted artifacts can then violate the intended integrity policy.
Summary
What happened
Cryptographic verification bypass in Sigstore sigstore-go before 1.2.0 allows remote attackers to defeat multi-log trust policies. VerifySignedCertificateTimestamp and VerifyTlogEntry count repeated SCT paths or entries without deduplicating the originating log authority. Exploitation requires a threshold above one and control of one trusted transparency or CT log; accepted artifacts can then violate the intended integrity policy.
The record
- CVE
- CVE-2026-49834
- Published
- Jul 17, 2026
- Updated
- Jul 17, 2026
- Vendor
- Sigstore
- Product
- sigstore-go
- Classifications
- CWE-347, T1553
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 17, 2026CVE publishedPublication date reported by the CVE source.
- Jul 17, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.2.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo