CVE-2026-40070

{"id": "CVE-2026-40070", "cveTags": [], "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 8.1, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "LOW", "confidentialityImpact": "HIGH"}, "impactScore": 5.2, "exploitabilityScore": 2.8}]}, "published": "2026-04-09T18:17:03.203", "references": [{"url": "https://brc.dev/52", "tags": ["Not Applicable"], "source": "security-advisories@github.com"}, {"url": "https://github.com/sgbett/bsv-ruby-sdk/commit/4992e8a265fd914a7eeb0405c69d1ff0122a84cc", "tags": ["Release Notes"], "source": "security-advisories@github.com"}, {"url": "https://github.com/sgbett/bsv-ruby-sdk/issues/305", "tags": ["Issue Tracking"], "source": "security-advisories@github.com"}, {"url": "https://github.com/sgbett/bsv-ruby-sdk/pull/306", "tags": ["Issue Tracking"], "source": "security-advisories@github.com"}, {"url": "https://github.com/sgbett/bsv-ruby-sdk/security/advisories/GHSA-hc36-c89j-5f4j", "tags": ["Exploit", "Patch", "Vendor Advisory"], "source": "security-advisories@github.com"}, {"url": "https://github.com/sgbett/bsv-ruby-sdk/security/advisories/GHSA-hc36-c89j-5f4j", "tags": ["Exploit", "Patch", "Vendor Advisory"], "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0"}], "vulnStatus": "Analyzed", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-347"}]}], "descriptions": [{"lang": "en", "value": "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."}], "lastModified": "2026-04-24T17:03:39.437", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:sgbett:bsv-wallet:*:*:*:*:*:ruby:*:*", "vulnerable": true, "matchCriteriaId": "64FDA9B4-4B7C-41B0-9736-991D19533DF6", "versionEndExcluding": "0.3.4", "versionStartIncluding": "0.1.2"}, {"criteria": "cpe:2.3:a:sgbett:bsv_ruby_sdk:*:*:*:*:*:ruby:*:*", "vulnerable": true, "matchCriteriaId": "634CB7F0-563B-42FC-BCF4-3F222AA63921", "versionEndExcluding": "0.8.2", "versionStartIncluding": "0.3.1"}], "operator": "OR"}]}], "sourceIdentifier": "security-advisories@github.com"}