CVE-2026-107853 json
tiny-secp256k1: Stale buffer after ignored wasm failure accepts invalid infinity tweak
published 22d ago modified 18h ago also GHSA-hj9c-qx2w-g7mh , EUVD-2026-127356
Unreviewed: the maintainers' own advisory
Published by the maintainers on their GitHub repository bitcoinjs/tiny-secp256k1. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.
- cvss
- 6.3
- version 4.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 43%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- npm tiny-secp256k1 2.2.5
- npm @bitcoin-js/tiny-secp256k1-asmjs 2.2.5
Is CVE-2026-107853 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
0.51% chance of exploitation in the next 30 days, higher than 43% of all scored CVEs (FIRST EPSS, 2026-11-18).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 6.3 | CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N |
| CNA | 4.0 | 6.3 | CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | tiny-secp256k1 | >=2.1.0, <2.2.5 |
2.2.5 |
| npm | @bitcoin-js/tiny-secp256k1-asmjs | >=2.2.2, <2.2.5 |
2.2.5 |
Affected products
- bitcoinjs tiny-secp256k1
- @bitcoin-js iny-secp256k1-asmjs
Classification
- Weakness
-
- CWE-252 Unchecked Return Value
References
Sources
- CVE List CVE-2026-107853
- NVD CVE-2026-107853
- Maintainer advisory GHSA-hj9c-qx2w-g7mh
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of bitcoinjs/tiny-secp256k1 published their own advisory on GitHub. Reviewed sources take precedence over it.