Skip to content

CVE-2026-40070

Sgbett Bsv Ruby Sdk vulnerability

8.1 HIGHPublic exploitEPSS 0.20%
  1. Published9 Apr 2026

Description

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's signature over the certificate contents. In acquisition_protocol: 'direct', the caller supplies all certificate fields (including signature:) and the record is written to storage verbatim. In acquisition_protocol: 'issuance', 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.

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredLow
User interactionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityNone
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Affected products

Sgbett Bsv Ruby Sdk≥ 0.3.1 < 0.8.2
Sgbett Bsv-wallet≥ 0.1.2 < 0.3.4

Remediation

Fixed in
Sgbett Bsv Ruby Sdk≥ 0.8.2
Sgbett Bsv-wallet≥ 0.3.4

Frequently asked

Is CVE-2026-40070 being actively exploited?

CVE-2026-40070 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.20%.

How severe is CVE-2026-40070?

CVE-2026-40070 has a CVSS 3.1 base score of 8.1, rated high. EPSS estimates a 0.20% probability of exploitation.

Which products are affected by CVE-2026-40070?

Affected products include Sgbett Bsv Ruby Sdk, Sgbett Bsv-wallet.

How do I fix CVE-2026-40070?

Upgrade affected software to a fixed version, for example Sgbett Bsv Ruby Sdk 0.8.2, Sgbett Bsv-wallet 0.3.4 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-40070 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.