Credential forgery via unverified certifier signatures
Published Apr 9, 2026 · Updated Apr 9, 2026
Improper signature verification in BSV Ruby SDK before 0.8.2 and bsv-wallet before 0.3.4 allows attackers to forge identity certificates. WalletClient#acquire_certificate writes caller- or endpoint-supplied signatures to storage without checking them against the claimed certifier's key. Reachability requires access to the acquisition API or control of its issuance endpoint; stored forgeries are trusted by list_certificates and prove_certificate.
Summary
What happened
Improper signature verification in BSV Ruby SDK before 0.8.2 and bsv-wallet before 0.3.4 allows attackers to forge identity certificates. WalletClient#acquire_certificate writes caller- or endpoint-supplied signatures to storage without checking them against the claimed certifier's key. Reachability requires access to the acquisition API or control of its issuance endpoint; stored forgeries are trusted by list_certificates and prove_certificate.
The record
- CVE
- CVE-2026-40070
- Published
- Apr 9, 2026
- Updated
- Apr 9, 2026
- Vendor
- BSV Blockchain
- Product
- BSV Ruby SDK
- Classifications
- CWE-347, T1649
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 9, 2026CVE publishedPublication date reported by the CVE source.
- Apr 9, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 0.3.1, < 0.8.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GHSA acquire_certificate proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo