Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-56744

Vulnerability in @bsv/wallet-toolbox (CVE-2026-56744)

Summary

Vulnerability in @bsv/wallet-toolbox (CVE-2026-56744). Risk of unauthorized operations or information disclosure. Exploitable via createAction. Mitigation: upgrade to 2.4.0 or later.

Original description

The description as published by the source.

Reported by @echennells (Eric Chennells). Migrated from public issue #191 to a private advisory.

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

Summary:
When 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.

Relevant code:

  • signer/methods/buildSignableTransaction.js — non-change output lockingScript = asBsvSdkScript(out.lockingScript), sourced from the storage response; args.outputs is not consulted.
  • WalletPermissionsManager.js createAction — parses the built tx, derives spend from args.outputs satoshis + tx.getFee(), reads tx.inputs; does not read tx.outputs.
  • signer/methods/signAction.js, completeSignedTransaction.js — sign the as-built tx; no output comparison.

Context:
Remote storage is a su…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-56744 has been found in @bsv/wallet-toolbox.
Attackers can target a specific entry point like createAction over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade @bsv/wallet-toolbox to 2.4.0 or later.
If unsure, ask your IT team or search "@bsv/wallet-toolbox CVE-2026-56744" on the vendor's site.

CVE-2026-56744 (@bsv/wallet-toolbox) — CWE-1288
Attack surface: createAction / StorageClient / buildSignableTransaction / lockingScript
Patched: 2.4.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-1288) exists in @bsv/wallet-toolbox. Attackers reach the vulnerable code path via createAction.

📍 Affected scope

Check the vendor advisory for the affected versions of @bsv/wallet-toolbox. Attack surface: createAction / StorageClient / buildSignableTransaction / lockingScript.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 2.4.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@bsv/wallet-toolbox' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r '@bsv/wallet-toolbox' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で @bsv/wallet-toolbox を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade @bsv/wallet-toolbox to 2.4.0

    ステージング環境で 2.4.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

npm @bsv/wallet-toolbox
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.4.0"}]}]
npm @bsv/wallet-toolbox-client
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.4.0"}]}]
npm @bsv/wallet-toolbox-mobile
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.4.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details