CVE-2026-107853
tiny-secp256k1: Stale buffer after ignored wasm failure accepts invalid infinity tweak
Description
tiny-secp256k1 is a tiny secp256k1 native/JS wrapper. From 2.1.0 until 2.2.5 for tiny-secp256k1 and from 2.2.2 until 2.2.5 for @bitcoin-js/tiny-secp256k1-asmjs, the three-argument xOnlyPointAddTweakCheck path ignores the backend failure return from xOnlyPointAddTweak when a tweak produces the point at infinity. The shared X_ONLY_PUBLIC_KEY_INPUT buffer then still contains the original point, so a caller-controlled resultToCheck equal to that point can make the stale-buffer comparison return true even though no tweaked key exists. Protocols that rely on this helper to validate caller-controlled internal keys, tweaks, and comparison values can accept an invalid derived key. This issue is fixed in version 2.2.5.
INFO
Published Date :
Nov. 17, 2026, 7:23 p.m.
Last Modified :
Nov. 17, 2026, 7:23 p.m.
Remotely Exploit :
No
Source :
GitHub_M
Solution
- Update tiny-secp256k1 to version 2.2.5 or later.
- Verify cryptographic operations after updating.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-107853 vulnerability anywhere in the article.