Transaction integrity loss via omitted ARC failure states
Published Apr 9, 2026 · Updated Apr 9, 2026
Improper exceptional-condition handling in BSV Ruby SDK 0.1.0 through 0.8.1 allows remote attackers to falsify broadcast success. The BSV::Network::ARC failure predicate accepts INVALID, MALFORMED, MINED_IN_STALE_BLOCK, and ORPHAN-bearing responses as successful broadcasts. Reachability requires an application to rely on that broadcaster result, allowing rejected transactions to trigger downstream integrity-sensitive actions.
Summary
What happened
Improper exceptional-condition handling in BSV Ruby SDK 0.1.0 through 0.8.1 allows remote attackers to falsify broadcast success. The BSV::Network::ARC failure predicate accepts INVALID, MALFORMED, MINED_IN_STALE_BLOCK, and ORPHAN-bearing responses as successful broadcasts. Reachability requires an application to rely on that broadcaster result, allowing rejected transactions to trigger downstream integrity-sensitive actions.
The record
- CVE
- CVE-2026-40069
- Published
- Apr 9, 2026
- Updated
- Apr 9, 2026
- Vendor
- BSV Blockchain
- Product
- BSV Ruby SDK
- Classifications
- CWE-754, T1565.002
- Attack vector
- network
- Privileges
- unauthenticated
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.1.0, < 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
No public exploit references are available in this record.
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