CVE-2026-31830: 
Ruby vulnerability analysis and mitigation

CVE-2026-31830 is an unchecked return value vulnerability in sigstore-ruby, a pure Ruby implementation of the sigstore verify command from the sigstore/cosign project. The flaw causes Sigstore::Verifier#verify to return VerificationSuccess for DSSE bundles containing in-toto statements even when the artifact digest does not match the attested subject digest. It affects all sigstore-ruby versions prior to 0.2.3 (RubyGems package sigstore). The vulnerability was published on March 10, 2026, and carries a CVSS v3.1 base score of 7.5 (High) (GitHub Advisory, Sigstore Advisory).

The root cause is CWE-252 (Unchecked Return Value): in lib/sigstore/verifier.rb, the verify method calls verify_in_toto(input, in_toto) at line 176 without capturing or acting on its return value. When verify_in_toto detects a digest mismatch between the artifact and the in-toto attestation subject, it returns a VerificationFailure object, but because the caller discards this return value, execution falls through unconditionally to return VerificationSuccess. This is the only one of 12 verification sub-checks in the method whose failure is not propagated; the message_signature code path is unaffected. All other checks — DSSE envelope signature, certificate chain, Rekor inclusion, SCTs, and policy — are independent of artifact content and therefore pass normally (Sigstore Advisory, GitHub Advisory).

The primary impact is a high-severity integrity violation: an attacker who possesses a valid signed DSSE bundle attesting to artifact A can present it as a valid attestation for a completely different artifact B, and the verifier will return success. This effectively breaks artifact-to-attestation binding for any consumer relying on Sigstore::Verifier#verify to validate DSSE/in-toto bundles, enabling tampered or malicious artifacts to bypass software supply chain verification controls. There is no confidentiality or availability impact, but the integrity compromise could lead to deployment of unauthorized or malicious code in pipelines that trust sigstore-ruby verification results (Sigstore Advisory, GitHub Advisory).

No public proof-of-concept exploit code is known to exist, and there is no evidence of in-the-wild exploitation at this time (GitHub Advisory). The EPSS score is approximately 0.045% (14th percentile), indicating a low near-term exploitation probability. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. Exploitation requires an attacker to already possess a legitimately signed DSSE bundle for one artifact, which they then reuse against a different artifact — a realistic threat in supply chain attack scenarios.

1. Obtain a valid signed DSSE bundle: Acquire a legitimately signed DSSE bundle containing an in-toto attestation for a known artifact A (e.g., a publicly released package or container image with a valid Sigstore signature).
2. Prepare a malicious artifact: Create or obtain a different, potentially malicious artifact B whose digest does not match the in-toto attestation subject in the bundle obtained in step 1.
3. Present the mismatched bundle: Submit artifact B along with the DSSE bundle originally attesting to artifact A to a system or pipeline that uses Sigstore::Verifier#verify from a vulnerable version of sigstore-ruby (< 0.2.3) for verification.
4. Bypass verification: The verifier calls verify_in_toto, which detects the digest mismatch and returns VerificationFailure, but because the return value is discarded, the verifier proceeds to return VerificationSuccess — all other checks (signature, certificate chain, Rekor, SCTs, policy) pass since they are independent of artifact content.
5. Achieve objective: The malicious artifact B is accepted as verified, potentially allowing it to be deployed, installed, or trusted within the target software supply chain pipeline (Sigstore Advisory).

• Logs: Verification success results logged for artifacts whose digests do not match the in-toto attestation subject in the associated DSSE bundle; audit logs showing VerificationSuccess for artifacts that were not the original attested subject.
• File System: Presence of unexpected or unrecognized artifacts (binaries, gems, container images) in deployment directories that carry valid-looking Sigstore attestations referencing a different artifact's digest.
• Process/Pipeline: CI/CD pipeline steps that invoke sigstore-ruby verification passing for artifacts that differ from the originally signed content; discrepancies between artifact checksums recorded at build time and those present at deployment.

The vulnerability is fixed in sigstore-ruby version 0.2.3; all users should upgrade immediately by running gem update sigstore or updating their Gemfile.lock to reference sigstore >= 0.2.3. No configuration-based workaround exists — consumers cannot mitigate this issue without patching the library. After upgrading, organizations should review any artifacts verified using vulnerable versions to confirm they were legitimate, and consider implementing additional audit logging around artifact verification processes (Sigstore Advisory, GitHub Advisory).

The vulnerability was credited to researcher hanazuki as the finder and published by Hayden-IO via the sigstore/sigstore-ruby GitHub Security Advisory on March 10, 2026 (Sigstore Advisory). A post on Bluesky referencing the CVE was observed in early April 2026, indicating some community awareness. No major vendor statements or significant media coverage beyond the advisory itself have been identified.