Vulnerabilities in pkg:npm/@bsv/wallet-toolbox
PACKAGECVE-2026-56744 is a HIGH `@bsv/wallet-toolbox` / `-client` / `-mobile` vulnerability (CWE-1288: Improper Validation of Consistency within Input) affecting @bsv/wallet toolbox libraries in the npm ecosystem. The issue involves `@bsv/wallet-toolbox` / `-client` / `-mobile` don't verify storage-supplied recipient output scripts against caller-requested outputs in createaction. Remediation is available by upgrading affected packages to version 2.4.0.
pkg:npm/@bsv/wallet-toolbox
Vulnerability advisories affecting package pkg:npm/@bsv/wallet-toolbox. Select an advisory below to view technical details or fixes.
| Advisory ID | CVE / NVD | Severity | Summary |
|---|---|---|---|
| GHSA-36f9-7rg5-cpf8 | CVE-2026-56744 | HIGH | `@bsv/wallet-toolbox` / `-client` / `-mobile` don't verify storage-supplied recipient output scripts against caller-requested outputs in createAction |
CVE-2026-56744 at a Glance
How to Fix CVE-2026-56744
To remediate this vulnerability, upgrade all affected @bsv/wallet toolbox dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
npm install @bsv/wallet-toolbox@2.4.0
npm install @bsv/wallet-toolbox-client@2.4.0
npm install @bsv/wallet-toolbox-mobile@2.4.0
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
npm ls @bsv/wallet-toolbox
How to Check if You Are Affected
To determine whether your Node.js application is affected by CVE-2026-56744, inspect your project dependencies using npm:
npm ls @bsv/wallet-toolbox
Analyze the terminal output to locate any version of @bsv/wallet toolbox in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.4.0), your application is affected.
Note: The npm ls @bsv/wallet-toolbox command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-1288: Improper Validation of Consistency within Input, where the product receives a complex input with multiple elements or fields that must be consistent with each other, but it does not validate or incorrectly validates that the input is actually consistent. In @bsv/wallet toolbox, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-56744 Affected @bsv/wallet toolbox Versions
3 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
@bsv/wallet-toolbox
|
npm |
≥ 1.1.47
< 2.4.0
|
2.4.0
|
|
@bsv/wallet-toolbox-client
|
npm |
≥ 1.1.47
< 2.4.0
|
2.4.0
|
|
@bsv/wallet-toolbox-mobile
|
npm |
≥ 1.3.21
< 2.4.0
|
2.4.0
|
References
Frequently Asked Questions
What is CVE-2026-56744?
Which @bsv/wallet toolbox versions are affected?
What version fixes CVE-2026-56744?
Is @bsv/wallet-toolbox affected?
Is @bsv/wallet-toolbox-client affected?
What CWE is associated with CVE-2026-56744?
How can I check npm dependencies for CVE-2026-56744?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-36f9-7rg5-cpf8",
"modified" : "2026-09-24T19:32:00Z",
"published" : "2026-09-24T19:32:00Z",
"aliases" : [ "CVE-2026-56744" ],
"summary" : "`@bsv/wallet-toolbox` / `-client` / `-mobile` don't verify storage-supplied recipient output scripts against caller-requested outputs in createAction",
"details" : "Reported by @echennells (Eric Chennells). Migrated from public issue #191 to a private advisory.\n\n**Affected:** `@bsv/wallet-toolbox` / `-client` / `-mobile`. Verified in `2.1.21` and `2.1.21-parity-fix.2`; the relevant code is the same at current HEAD\n\n**Summary:**\nWhen `createAction` runs against a remote `StorageClient`, the storage server returns the outputs to build. `buildSignableTransaction` takes each non-change output's `lockingScript` from the storage response and signs it, without comparing it to the `lockingScript` the caller supplied in `args.outputs`. `WalletPermissionsManager.createAction` parses the built transaction and has `args.outputs` available, but uses the tx only for `inputs` and `getFee()`; it does not inspect `tx.outputs`. A storage provider that returns a different recipient script than requested will therefore have that script signed and broadcast, while the calling app and UI still show the originally requested recipient.\n\n**Relevant code:**\n - `signer/methods/buildSignableTransaction.js` — non-change output `lockingScript = asBsvSdkScript(out.lockingScript)`, sourced from the storage response; `args.outputs` is not consulted.\n - `WalletPermissionsManager.js` `createAction` — parses the built tx, derives spend from `args.outputs` satoshis + `tx.getFee()`, reads `tx.inputs`; does not read `tx.outputs`.\n - `signer/methods/signAction.js`, `completeSignedTransaction.js` — sign the as-built tx; no output comparison.\n\n**Context:**\nRemote storage is a supported, default configuration (`StorageClient` over BRC-103 `AuthFetch`, default endpoint `storage.babbage.systems`, optional payment middleware). The mutual auth establishes the storage server's identity and protects the channel, but the contents it returns are not validated against the request. The attacker is the storage operator, or anyone who compromises it — not a passive network MITM. (`StorageServer.processAction` does compare the signed rawTx outputs to what storage stored, so a response-only MITM is rejected; an operator stores the substituted script from the start.)\n\n**Proof of concept:**\nWe ran a storage server that returns a substituted recipient output, and pointed a current yours-wallet build at it as its active storage provider. With the wallet otherwise unmodified, a payment requested to one address was built, signed, and broadcast paying a different address, the substitution was not surfaced anywhere in the wallet.",
"severity" : [ {
"type" : "CVSS_V4",
"score" : "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"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "npm",
"name" : "@bsv/wallet-toolbox"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "1.1.47"
}, {
"fixed" : "2.4.0"
} ]
} ]
}, {
"package" : {
"ecosystem" : "npm",
"name" : "@bsv/wallet-toolbox-client"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "1.1.47"
}, {
"fixed" : "2.4.0"
} ]
} ]
}, {
"package" : {
"ecosystem" : "npm",
"name" : "@bsv/wallet-toolbox-mobile"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "1.3.21"
}, {
"fixed" : "2.4.0"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/bsv-blockchain/ts-stack/security/advisories/GHSA-36f9-7rg5-cpf8"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-56744"
}, {
"type" : "WEB",
"url" : "https://github.com/bsv-blockchain/ts-stack/commit/3a11f6111919245a3090e9f3895cfc4f21a80d28"
}, {
"type" : "WEB",
"url" : "https://github.com/bsv-blockchain/ts-stack/commit/5492cabbef4ddc7f60cc49cdf5d8c74ed2e5d949"
}, {
"type" : "WEB",
"url" : "https://github.com/bsv-blockchain/ts-stack/commit/5ee60395e78e8b822d9a78efeacc6039c249819b"
}, {
"type" : "WEB",
"url" : "https://github.com/bsv-blockchain/wallet-toolbox/commit/ca651b067c0238cd8b1ddd3af225daa503857a07"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/bsv-blockchain/ts-stack"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-1288" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2026-09-24T19:32:00Z",
"nvd_published_at" : "2026-09-24T17:17:05Z"
}
}