CVE-2026-31830
Verification Bypass in sigstore-ruby Prior to
Publication date: 2026-03-10
Last updated on: 2026-03-20
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| sigstore | sigstore | to 0.2.3 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-252 | The product does not check the return value from a method or function, which can prevent it from detecting unexpected states and conditions. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The vulnerability exists in the sigstore-ruby library prior to version 0.2.3. Specifically, the method Sigstore::Verifier#verify does not properly propagate a VerificationFailure error when the artifact digest does not match the digest in the in-toto attestation subject. This means that even if the artifact does not match the attested subject, the verification process incorrectly returns a VerificationSuccess.
How can this vulnerability impact me? :
This vulnerability can lead to false verification success results when verifying DSSE bundles containing in-toto statements. As a result, an attacker could potentially present an artifact that does not match the attested subject, but it would still be accepted as valid. This undermines the integrity verification process and could allow unauthorized or tampered artifacts to be trusted.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, upgrade sigstore-ruby to version 0.2.3 or later, where the issue with verification propagation is fixed.