Skip to main content
VulnerabilityPublished

CVE-2026-107853: tiny-secp256k1 · Stale buffer after ignored wasm failure accepts invalid infinity tweak

Affects tiny-secp256k1Source GCVE Database

0
Compare
Authoritative record:CVE-2026-107853· Medium 6.3

Not known to be exploited · CVSS 6.3 Medium : upgrade to 2.2.5 when convenient.

Data as of 19 Nov 2026, 23:23 UTC

CVSS 4.0 base score
6.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 4.06.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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 19 Nov 2026.

What to do

Upgrade tiny-secp256k1 and @bitcoin-js/tiny-secp256k1-asmjs to 2.2.5.

Affected software

ProductAffectedFixed in
npmtiny-secp256k1Affected
  • >=2.1.0 <2.2.5
Fixed in
  • 2.2.5
npm@bitcoin-js/tiny-secp256k1-asmjsAffected
  • >=2.2.2 <2.2.5
Fixed in
  • 2.2.5

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in tiny-secp256k1 version 2.2.5. Users should upgrade to version 2.2.5 or later to address this vulnerability. No additional mitigation actions are required beyond applying the official patch.

Description

A vulnerability in tiny-secp256k1 versions >=2.1.0 <2.2.5 and >=2.2.2 <2.2.5 allows an invalid tweak operation to be accepted due to a stale buffer comparison after a wasm failure. Specifically, the three-argument form of xOnlyPointAddTweakCheck ignores the wasm failure return and compares an unchanged input buffer, causing it to incorrectly validate an invalid derivation when the tweak results in the point at infinity. This flaw is fixed in version 2.2.5.

References

Community reviews

Loading reviews…