{"answers":{"affected":"2 open source packages ship an affected version, including sigstore. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-31830 in the wild and no public exploit code.","fix":"Upgrade sigstore to 0.2.3 or later.","what":"CVE-2026-31830 is a high-severity vulnerability in sigstore-ruby, published on 10 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-31830 and fix it if it is affected.\n\nWhat it is: CVE-2026-31830 is a high-severity vulnerability in sigstore-ruby, published on 10 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-31830 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- sigstore (RubyGems): affected all versions; fixed in 0.2.3\n- sigstore (RubyGems): affected all versions; fixed in 0.2.3\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-31830/ (Markdown: https://insights.sbomify.com/CVE-2026-31830/index.md)","id":"CVE-2026-31830","markdown":"https://insights.sbomify.com/CVE-2026-31830/index.md","name":"CVE-2026-31830","record":{"aliases":["GHSA-mhg6-2q2v-9h2c"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Ruby signature verification library","requires_auth":"none","summary":"Attackers can bypass signature verification in sigstore-ruby by providing mismatched artifact digests, allowing unsigned or tampered code to appear valid.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"sigstore","vendor":"sigstore"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-252","name":"Unchecked Return Value"}],"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.","ecosystems":["RubyGems"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"sigstore-ruby verifier returns success for DSSE bundles with mismatched in-toto subject digest","id":"CVE-2026-31830","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"RubyGems","product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":2,"n_references":1,"next":{"headline":"Tautulli: Unauthenticated Path Traversal in `/newsletter/image/images` endpoint","id":"CVE-2026-31831"},"packages":[{"ecosystem":"RubyGems","fixed":["0.2.3"],"introduced":["0"],"last_affected":[],"package":"sigstore","purl":null,"source":"GHSA-mhg6-2q2v-9h2c"},{"ecosystem":"RubyGems","fixed":["0.2.3"],"introduced":["0"],"last_affected":[],"package":"sigstore","purl":"pkg:gem/sigstore","source":"GHSA-mhg6-2q2v-9h2c"}],"prev":{"headline":"Flowise affected by Server-Side Request Forgery (SSRF) in HTTP Node Leading to Internal Network Access","id":"CVE-2026-31829"},"products":["sigstore-ruby"],"published":"2026-03-10","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-11","vendors":["sigstore"]},"summary":"Attackers can bypass signature verification in sigstore-ruby by providing mismatched artifact digests, allowing unsigned or tampered code to appear valid.","url":"https://insights.sbomify.com/CVE-2026-31830/"}