https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Thu, 08 Oct 2026 15:51:54 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-290891 EUVD-2026-290891 https://cve.radiocsirt.org/vuln/euvd-2026-290891 https://cve.radiocsirt.org/vuln/fkie_cve-2026-40070 <p>BSV Ruby SDK is the Ruby SDK for the BSV blockchain. From 0.3.1 to before 0.8.2, BSV::Wallet::WalletClient#acquire_certificate persists certificate records to storage without verifying the certifier&#39;s signature over the certificate contents. In acquisition_protocol: &#39;direct&#39;, the caller supplies all certificate fields (including signature:) and the record is written to storage verbatim. In acquisition_protocol: &#39;issuance&#39;, the client POSTs to a certifier URL and writes whatever signature the response body contains, also without verification. An attacker who can reach either API (or who controls a certifier endpoint targeted by the issuance path) can forge identity certificates that subsequently appear authentic to list_certificates and prove_certificate.</p> <p>BSV Ruby SDK is the Ruby SDK for the BSV blockchain. From 0.3.1 to before 0.8.2, BSV::Wallet::WalletClient#acquire_certificate persists certificate records to storage without verifying the certifier&#39;s signature over the certificate contents. In acquisition_protocol: &#39;direct&#39;, the caller supplies all certificate fields (including signature:) and the record is written to storage verbatim. In acquisition_protocol: &#39;issuance&#39;, the client POSTs to a certifier URL and writes whatever signature the response body contains, also without verification. An attacker who can reach either API (or who controls a certifier endpoint targeted by the issuance path) can forge identity certificates that subsequently appear authentic to list_certificates and prove_certificate.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-40070 https://cve.radiocsirt.org/vuln/ghsa-hc36-c89j-5f4j <p><strong>Affected:</strong> RubyGems: bsv-sdk, RubyGems: bsv-wallet</p> <p># Unverified certifier signatures persisted by `acquire_certificate`</p> <p>## Affected packages</p> <p>Both `bsv-sdk` and `bsv-wallet` are published from the [sgbett/bsv-ruby-sdk](https://github.com/sgbett/bsv-ruby-sdk) repository. The vulnerable code lives in `lib/bsv/wallet_interface/wallet_client.rb`, which is **physically shipped inside both gems** (the `bsv-wallet.gemspec` `files` list bundles the entire `lib/bsv/wallet_interface/` tree). Consumers of either gem are independently vulnerable; the two packages are versioned separately, so each has its own affected range.</p> <p>| Package | Affected | Patched | | --- | --- | --- | | `bsv-sdk` | `&gt;= 0.3.1, &lt; 0.8.2` | `0.8.2` | | `bsv-wallet` | `&gt;= 0.1.2, &lt; 0.3.4` | `0.3.4` |</p> <p>## Summary</p> <p>`BSV::Wallet::WalletClient#acquire_certificate` persists certificate records to storage **without verifying the certifier&#39;s signature** over the certificate contents. Both acquisition paths are affected:</p> <p>- `acquisition_protocol: &#39;direct&#39;` — the caller supplies all certificate fields (including `signature:`) and the record is written to storage verbatim. - `acquisition_protocol: &#39;issuance&#39;` — the client POSTs to a certifier URL and writes whatever signature the response body contains, also without verification.</p> <p>An attacker who can reach either API (or who controls a certifier endpoint targeted by the issuance path) can forge identity certificates that subsequently appear authentic to `list_certificates` and `prove_certificate`.</p> <p>## Details</p> <p>BRC-52 requires…</p> <p><strong>Affected:</strong> RubyGems: bsv-sdk, RubyGems: bsv-wallet</p> <p># Unverified certifier signatures persisted by `acquire_certificate`</p> <p>## Affected packages</p> <p>Both `bsv-sdk` and `bsv-wallet` are published from the [sgbett/bsv-ruby-sdk](https://github.com/sgbett/bsv-ruby-sdk) repository. The vulnerable code lives in `lib/bsv/wallet_interface/wallet_client.rb`, which is **physically shipped inside both gems** (the `bsv-wallet.gemspec` `files` list bundles the entire `lib/bsv/wallet_interface/` tree). Consumers of either gem are independently vulnerable; the two packages are versioned separately, so each has its own affected range.</p> <p>| Package | Affected | Patched | | --- | --- | --- | | `bsv-sdk` | `&gt;= 0.3.1, &lt; 0.8.2` | `0.8.2` | | `bsv-wallet` | `&gt;= 0.1.2, &lt; 0.3.4` | `0.3.4` |</p> <p>## Summary</p> <p>`BSV::Wallet::WalletClient#acquire_certificate` persists certificate records to storage **without verifying the certifier&#39;s signature** over the certificate contents. Both acquisition paths are affected:</p> <p>- `acquisition_protocol: &#39;direct&#39;` — the caller supplies all certificate fields (including `signature:`) and the record is written to storage verbatim. - `acquisition_protocol: &#39;issuance&#39;` — the client POSTs to a certifier URL and writes whatever signature the response body contains, also without verification.</p> <p>An attacker who can reach either API (or who controls a certifier endpoint targeted by the issuance path) can forge identity certificates that subsequently appear authentic to `list_certificates` and `prove_certificate`.</p> <p>## Details</p> <p>BRC-52 requires…</p> https://cve.radiocsirt.org/vuln/ghsa-hc36-c89j-5f4j