Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

RubyGems package

bsv-wallet

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 8.1RubyGemsPublished

    bsv-sdk and bsv-wallet persist unverified certifier signatures in acquire_certificate (direct and issuance paths)

    CVE-2026-40070 · GHSA-hc36-c89j-5f4j

    Affected
    • RubyGems bsv-wallet >= 0.1.2, < 0.3.4
    Fixed in
    0.3.4· Vendor fix available
    Issue
    Unverified certifier signatures persisted by acquirecertificate Affected packages Both bsv-sdk and bsv-wallet are published from the sgbett/bsv-ruby-sdk repository. The vulnerable code lives in lib/bsv/walletinterface/walletclient.rb, which is physically shipped inside both gems (the bsv-wallet.gemspec files list bundles the entire lib/bsv/walletinterface/ tree). Consumers of either gem are independently vulnerable; the two packages are versioned separately, so each has its own affected range. | Package | Affected | Patched | | --- | --- | --- | | bsv-sdk | = 0.3.1, < 0.8.2 | 0.8.2 | | bsv-wallet | = 0.1.2, < 0.3.4 | 0.3.4 | Summary BSV::Wallet::WalletClient#acquirecertificate persists certificate records to storage without verifying the certifier's signature over the certificate contents. Both acquisition paths are affected: - acquisitionprotocol: 'direct' — the caller supplies all certificate fields (including signature:) and the record is written to storage verbatim. -…

    Recommended action: Upgrade to 0.3.4 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →