CVE-2026-107853: bitcoinjs tiny-secp256k1 · Unchecked Return Value
Affects bitcoinjs tiny-secp256k1Source CVE Database V5
Not known to be exploited · CVSS 6.3 Medium : upgrade to 2.2.5 when convenient.
Data as of 17 Nov 2026, 19:36 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 4.0 | 6.3 |
|---|
- Patch
- Available – fixed in 2.2.5
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 17 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.
What to do
Upgrade tiny-secp256k1 and iny-secp256k1-asmjs to 2.2.5.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| bitcoinjstiny-secp256k1 | Affected
| Fixed in
|
| @bitcoin-jsiny-secp256k1-asmjs | Affected
| Fixed in
|
AI-suggested
Upgrade to tiny-secp256k1 version 2.2.5 or later, where the issue is fixed. No other mitigations are indicated or required.
Description
A vulnerability in tiny-secp256k1 versions 2.1.0 through 2.2.4 and @bitcoin-js/tiny-secp256k1-asmjs versions 2.2.2 through 2.2.4 allows invalid derived keys to be accepted due to unchecked return values in the xOnlyPointAddTweakCheck function. This occurs when a tweak produces the point at infinity, causing the function to ignore backend failure and potentially validate a stale buffer as a valid key. The issue is fixed in version 2.2.5.