{"answers":{"affected":"2 open source packages ship an affected version, including bsv-sdk. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-40069 in the wild and no public exploit code.","fix":"Upgrade bsv-sdk to 0.8.2 or later.","what":"CVE-2026-40069 is a high-severity vulnerability in sgbett bsv-ruby-sdk, published on 9 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-40069 and fix it if it is affected.\n\nWhat it is: CVE-2026-40069 is a high-severity vulnerability in sgbett bsv-ruby-sdk, published on 9 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-40069 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- bsv-sdk (RubyGems): affected from 0.1.0; fixed in 0.8.2\n- bsv-sdk (RubyGems): affected from 0.1.0; fixed in 0.8.2\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-40069/ (Markdown: https://insights.sbomify.com/CVE-2026-40069/index.md)","id":"CVE-2026-40069","markdown":"https://insights.sbomify.com/CVE-2026-40069/index.md","name":"CVE-2026-40069","record":{"aliases":["GHSA-9hfr-gw99-8rhx"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify","other"],"network_reachable":"yes","non_default_config":false,"product_category":"BSV Ruby SDK","requires_auth":"none","summary":"The BSV Ruby SDK incorrectly treats invalid blockchain transactions as successful, potentially leading to data integrity issues in applications relying on broadcast confirmation.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"bsv_ruby_sdk","vendor":"sgbett"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-754","name":"Improper Check for Unusual or Exceptional Conditions"}],"description":"BSV Ruby SDK is the Ruby SDK for the BSV blockchain. From 0.1.0 to before 0.8.2, BSV::Network::ARC's failure detection only recognises REJECTED and DOUBLE_SPEND_ATTEMPTED. ARC responses with txStatus values of INVALID, MALFORMED, MINED_IN_STALE_BLOCK, or any ORPHAN-containing extraInfo / txStatus are silently treated as successful broadcasts. Applications that gate actions on broadcaster success are tricked into trusting transactions that were never accepted by the network. This vulnerability is fixed in 0.8.2.","ecosystems":["RubyGems"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"bsv-sdk ARC broadcaster treats INVALID/MALFORMED/ORPHAN responses as successful broadcasts","id":"CVE-2026-40069","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"RubyGems","product":null,"products":[],"type":"business_logic","year":"2026"},"n_packages":2,"n_references":5,"next":{"headline":"bsv-sdk and bsv-wallet persist unverified certifier signatures in acquire_certificate (direct and issuance paths)","id":"CVE-2026-40070"},"packages":[{"ecosystem":"RubyGems","fixed":["0.8.2"],"introduced":["0.1.0"],"last_affected":[],"package":"bsv-sdk","purl":null,"source":"GHSA-9hfr-gw99-8rhx"},{"ecosystem":"RubyGems","fixed":["0.8.2"],"introduced":["0.1.0"],"last_affected":[],"package":"bsv-sdk","purl":"pkg:gem/bsv-sdk","source":"GHSA-9hfr-gw99-8rhx"}],"prev":{"headline":"Claude Code arbitrary code execution via git worktree commondir trust dialog bypass","id":"CVE-2026-40068"},"products":["bsv-ruby-sdk"],"published":"2026-04-09","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-13","vendors":["sgbett"]},"summary":"The BSV Ruby SDK incorrectly treats invalid blockchain transactions as successful, potentially leading to data integrity issues in applications relying on broadcast confirmation.","url":"https://insights.sbomify.com/CVE-2026-40069/"}