CVE-2026-40069: CWE-754: Improper Check for Unusual or Exceptional Conditions in sgbett bsv-ruby-sdk
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.
AI Analysis
Technical Summary
CVE-2026-40069 is an improper check for unusual or exceptional conditions (CWE-754) in the sgbett bsv-ruby-sdk, specifically in versions >= 0.1.0 and < 0.8.2. The vulnerability arises because the failure detection in BSV::Network::ARC only recognizes two failure statuses (REJECTED and DOUBLE_SPEND_ATTEMPTED) and treats other failure statuses such as INVALID, MALFORMED, MINED_IN_STALE_BLOCK, or ORPHAN-containing extraInfo/txStatus as successful broadcasts. This flaw can lead to applications trusting transactions that were never accepted by the BSV blockchain network. The vulnerability has a CVSS 3.1 base score of 7.5 (high severity) with network attack vector, low attack complexity, no privileges or user interaction required, unchanged scope, no confidentiality impact, high integrity impact, and no availability impact. The issue is resolved in version 0.8.2 of the SDK.
Potential Impact
Applications using affected versions of the bsv-ruby-sdk may incorrectly consider certain failed transactions as successfully broadcasted to the BSV blockchain network. This can lead to trusting invalid or malformed transactions, potentially causing incorrect application behavior or data integrity issues. There is no direct confidentiality or availability impact reported. The integrity of transaction processing is at risk.
Mitigation Recommendations
Upgrade to bsv-ruby-sdk version 0.8.2 or later, where this vulnerability is fixed. Patch status is confirmed by the vendor's versioning information in the description. No other mitigation steps are indicated or necessary once upgraded.
CVE-2026-40069: CWE-754: Improper Check for Unusual or Exceptional Conditions in sgbett bsv-ruby-sdk
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.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-40069 is an improper check for unusual or exceptional conditions (CWE-754) in the sgbett bsv-ruby-sdk, specifically in versions >= 0.1.0 and < 0.8.2. The vulnerability arises because the failure detection in BSV::Network::ARC only recognizes two failure statuses (REJECTED and DOUBLE_SPEND_ATTEMPTED) and treats other failure statuses such as INVALID, MALFORMED, MINED_IN_STALE_BLOCK, or ORPHAN-containing extraInfo/txStatus as successful broadcasts. This flaw can lead to applications trusting transactions that were never accepted by the BSV blockchain network. The vulnerability has a CVSS 3.1 base score of 7.5 (high severity) with network attack vector, low attack complexity, no privileges or user interaction required, unchanged scope, no confidentiality impact, high integrity impact, and no availability impact. The issue is resolved in version 0.8.2 of the SDK.
Potential Impact
Applications using affected versions of the bsv-ruby-sdk may incorrectly consider certain failed transactions as successfully broadcasted to the BSV blockchain network. This can lead to trusting invalid or malformed transactions, potentially causing incorrect application behavior or data integrity issues. There is no direct confidentiality or availability impact reported. The integrity of transaction processing is at risk.
Mitigation Recommendations
Upgrade to bsv-ruby-sdk version 0.8.2 or later, where this vulnerability is fixed. Patch status is confirmed by the vendor's versioning information in the description. No other mitigation steps are indicated or necessary once upgraded.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-04-09T00:39:12.204Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69d7e6ff1cc7ad14dafe8dda
Added to database: 4/9/2026, 5:50:55 PM
Last enriched: 4/17/2026, 11:54:49 AM
Last updated: 5/24/2026, 9:40:11 PM
Views: 68
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.