BSV Rust Toolkit 0.8.10 Adds Security Fixes for Application Data and Payments

BSV Rust Toolkit 0.8.10 Adds Security Fixes for Application Data and Payments
, ,

Developer Tools / Payments Infrastructure

In Brief

bsv-rs 0.8.10 strengthens how Rust-based applications check signed records and responses from services that submit payments to BSV Blockchain. The update is published for developers, with additional migration steps required for some stored records and transaction-reading functions.

News Report

Published on November 15 (UTC), the stable release lists fixes for nine security advisories. A tenth advisory concerns excessive memory use when reading a transaction: version 0.8.10 supplies new functions to limit that work, but applications continuing to use the older functions remain affected.

Checking Who Wrote a Record

Some of the toolkit’s data-reading functions could accept an unsigned record and attribute its value to the author named inside it. A separate weakness allowed previously signed data to be presented under a record name its author had not used. The consequences depended on whether an application trusted those returned records.

The updated checks require the appropriate signature and bind it to the specific entry being authenticated. These changes affect GlobalKVStore, the toolkit’s system for publishing and retrieving named data records, and the functions that interpret those records.

This also changes the treatment of legitimate older entries. The project instructs developers to retain their own trusted records before upgrading and publish the entries again afterward. Earlier records remain on the blockchain, but the updated readers no longer accept their old authentication format. The migration must use the publisher’s own records, rather than trusting a fresh lookup of potentially misleading data.

Following the Payment That Was Actually Sent

The release also fixes how the toolkit handles replies from WhatsOnChain and ARC broadcasting services. Previously, a successful response naming another transaction could be returned to the application without checking it against the transaction submitted.

An application relying on that answer could track the wrong payment, including an unrelated transaction already recorded in a block. Version 0.8.10 rejects a response whose transaction identifier does not match. This change concerns the toolkit’s handling of service replies; the advisory does not establish that either service supplied malicious responses.

Where an Upgrade Alone Is Insufficient

A separate issue affects Extended Format, a transaction format carrying information about the funds being spent. A relatively small incoming message can cause the existing reading functions to allocate excessive memory, potentially stopping an application or request.

Version 0.8.10 adds alternative readers that enforce an application-selected limit before making those allocations. Developers handling data from outside parties must adopt those readers, or perform equivalent checks beforehand. The original functions retain their behavior, and the advisory lists no fixed version for them.

Several advisories also cover published 0.9.0 prereleases. The latest published beta remains beta.7; a new beta containing all these fixes had not been published at the time of checking.

The maintainer reports regression and conformance tests, along with native and WebAssembly checks. These are project-reported results, and the disclosures do not identify an exploited consumer wallet.

BSV TIMES Read

Reliable applications depend on the meaning of returned data as well as whether a request succeeds. This release strengthens several of those checks, while showing why security maintenance can require changes to stored records and application behavior alongside a new package version.

Developer Context

GitHub contributor Calgooon prepared the stable-branch security changes. Maintained in the Calhooon/bsv-rs repository, the project provides Rust components for wallets, transactions, authentication and data services. The advisories credit the project’s own review and testing work with identifying the issues.

Source Links

Posted on November 16, 2026 (UTC)

Leave a Reply