Skip to content

v25.1.3

Latest

Choose a tag to compare

@github-actions github-actions released this 20 Nov 16:59
e6635e6

Taquito v25.1.3

Stable patch release of v25.1.3, published under the latest dist-tag.

TL;DR. v25.1.3 fixes commitment trapdoor (rcm) and spend randomizer reuse in @taquito/sapling multi-output and multi-input transactions (including single-recipient transfers with change) (#3588, GHSA-6r9w-cxjj-5776). It also rolls up v25.1.2, published earlier today, which fixed smart_rollup_originate whitelist decoding in @taquito/local-forging (LocalForger.parse()) (#3582, GHSA-9wjf-4grc-2g2h).

Project status. Taquito is an unfunded project maintained by ECAD Labs. Releases continue on a best-effort basis; protocol-tracking and critical security and reliability releases remain a priority.


Fixes in v25.1.3 (@taquito/sapling)

  • Advisory: GHSA-6r9w-cxjj-5776

  • Credit: Discovered, responsibly reported, and verified against the patched branches by Rahul Saxena (@saxenism) of Bluethroat Labs

  • Fresh per-output commitment trapdoor and per-input spend randomizer (#3588, backported from #3587):

    • SaplingTransactionBuilder previously sampled a single randomCommitmentTrapdoor (rcm) once per transaction in createShieldedTx and createSaplingTx and reused it across all outputs (including the payback/change output), and sampled a single publicKeyReRandomization randomizer once per prepareSaplingSpendDescription call instead of per spend input.
    • Each deposit, payment, and payback output now samples its own randomCommitmentTrapdoor, and each spend input samples its own publicKeyReRandomization, matching Octez's Sapling transaction builder.
  • Practical Scope (Mostly Academic):

    • While reusing randomness across Sapling outputs/inputs is a real cryptographic bug worth fixing, the practical risk to users is mostly academic: Tezos Sapling has effectively no real users on mainnet, and its shielded pools are ghost towns (nearly all empty or single-digit test pools) with no crowd to anonymize in anyway.

Also Included Since v25.1.1 (from v25.1.2)

Because v25.1.2 shipped just a couple of hours earlier without a separate announcement, its fix is summarized here as well:

  • Advisory: GHSA-9wjf-4grc-2g2h

  • Credit: Discovered and responsibly reported to security@ecadlabs.com by byfor (@byfor8 / https://x.com/byfor88).

  • Bounded whitelist decoding for smart_rollup_originate in @taquito/local-forging (LocalForger.parse()) (#3582):

    • publicKeyHashesDecoder now slices a bounded sub-buffer of the declared 4-byte length prefix instead of consuming the rest of the operation buffer; publicKeyHashDecoder throws OperationDecodingError on unknown tags, and truncated whitelist headers, payloads, or key hashes throw OperationDecodingError.
    • Low Exposure: Typical dApps, LocalForger.forge(), and standard Taquito operation preparation, signing, and injection flows are unaffected. This only affects wallets handling smart rollups and direct users of @taquito/local-forging calling LocalForger.parse() on raw forged operation bytes (such as 0x03 wallet signing payloads) when a multi-operation batch contains a smart_rollup_originate with a whitelist followed by trailing operations (or when decoding malformed whitelist bytes).

Upgrading

npm install @taquito/taquito@25.1.3 @taquito/sapling@25.1.3 @taquito/local-forging@25.1.3

(Or update whichever @taquito/* packages you consume directly to 25.1.3.)

Full Changelog: v25.1.1...v25.1.3