Tree News

Tezos · 2026-11-13 17:11 UTC

[Security] octez.connect v5.0.5: pairing and session-control fix 🔒 *Joint post by Nomadic Labs, TriliTech and Functori* octez.connect v5.0.5 fixes vulnerabilities in pairing and session-control validation inherited from the Beacon SDK. These issues do not expose wallet private keys and do not allow anyone to forge signatures from a user's wallet. ⚠️ Action required • dApps on @tezos-x/octez.connect-* ≤ 5.0.4 (incl. 4.8.x): upgrade to 5.0.5 • dApps on @tezos-x/octez.js-dapp-wallet 25.0.0 or 25.1.0-rc.0: upgrade to 25.0.1 or 25.1.0-rc.1 (octez.js release in progress) • Taquito with the ECAD packages: upgrade to @taquito/*@25.1.1 • Wallets built on the octez.connect wallet SDK: upgrade to 5.0.5 • Suspect your dApp was targeted? Clear stored peers and ask users to re-pair ℹ️ Behavior change Reloading the page while a pairing is in progress invalidates it: users will need a fresh QR code or deep link. Completed pairings restore normally. 🔧 What was fixed • Pairing responses must match a live, single-use pairing request, with its ID • Matrix room invites and routing are only trusted once the sender is authenticated • senderId is bound to the sender's key, ChangeAccountRequest is only accepted from the active peer, and Disconnect from an unknown wallet is ignored • Closing the pairing popup invalidates its QR code 🙏 Thanks To David Kaminski (@dvkam) for discovering and reporting these issues, and to ECAD Labs for the hardening, testing and coordinated disclosure, and for the fixed @ecadlabs/beacon-* and Taquito releases. 📖 Full announcement: < 💻 GitHub: < 📦 npm (octez.connect): < 📦 npm (octez.js): <

Loading the story on Tree News…