Artifact verification bypass via discarded digest failure
Published Mar 10, 2026 · Updated Mar 10, 2026
Artifact-verification bypass in Sigstore sigstore-ruby before 0.2.3 allows remote attackers to accept a mismatched DSSE attestation. Sigstore::Verifier#verify discards the VerificationFailure returned by verify_in_toto after an in-toto subject digest mismatch, then falls through to VerificationSuccess. Exploitation requires a valid signed DSSE bundle for one artifact and a consumer that relies on this method, allowing that attestation to be presented for a different artifact.
Summary
What happened
Artifact-verification bypass in Sigstore sigstore-ruby before 0.2.3 allows remote attackers to accept a mismatched DSSE attestation. Sigstore::Verifier#verify discards the VerificationFailure returned by verify_in_toto after an in-toto subject digest mismatch, then falls through to VerificationSuccess. Exploitation requires a valid signed DSSE bundle for one artifact and a consumer that relies on this method, allowing that attestation to be presented for a different artifact.
The record
- CVE
- CVE-2026-31830
- Published
- Mar 10, 2026
- Updated
- Mar 10, 2026
- Vendor
- Sigstore
- Product
- sigstore-ruby
- Classifications
- CWE-252, T1553
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 10, 2026CVE publishedPublication date reported by the CVE source.
- Mar 10, 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=< 0.2.3
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.
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