Bsv rs: Transaction::from_json holds an input txid that is not 64 hex digits and writes the input as spending the zero
Affects bsv-rsSource GCVE Database
CVSS 5.3 Medium : upgrade to 0.9.0-beta.7.0 or 0.8.6 when convenient.
Data as of 12 Nov 2026, 08:07 UTC
- Patch
- Available – fixed in 0.9.0-beta.7.0, 0.8.6
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:NWhat to do
Upgrade bsv-rs to 0.9.0-beta.7.0 or 0.8.6.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
crates.iobsv-rspkg:cargo/bsv-rsOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade to bsv-rs version 0.8.6 or later, or 0.9.0-beta.7.0 or later, where invalid input txids are rejected with an error. If upgrading is not possible, implement input validation to ensure each input's txid is exactly 64 ASCII hexadecimal digits before passing data to Transaction::from_json.
Description
The bsv-rs library's Transaction::from_json method improperly handles input transaction IDs (txid) that are not exactly 64 hexadecimal digits. When such invalid txids are parsed, the method returns Ok but internally treats the input as spending a zeroed-out txid, causing inconsistent transaction identification. This affects applications that parse peer transaction documents and rely on both textual and binary representations of inputs. Versions prior to 0.8.6 and certain beta versions before 0.9.0-beta.7.0 are affected. The issue is fixed in versions 0.8.6 and 0.9.0-beta.7.0.