Skip to content
tiny-secp256k1 CVE-2026-107853: stale-buffer check accepts invalid tweaked keys

tiny-secp256k1 CVE-2026-107853: stale-buffer check accepts invalid tweaked keys

First seen 22 Nov 2026, 13:12 UTC • •

Article Content

Browse articles
ThreatCluster AI
ThreatCluster •November 22, 2026 at 13:13 UTC
  • •Affected: tiny-secp256k1 2.1.0 to 2.2.4 and @bitcoin-js/tiny-secp256k1-asmjs 2.2.2 to 2.2.4.
  • •Flaw: a failed tweak yielding the point at infinity leaves a stale buffer, so the check can return true for invalid derivations.
  • •Fixed in tiny-secp256k1 2.2.5 (commit ba1af1fc, GHSA-hj9c-qx2w-g7mh); upgrade affected wallet and protocol dependencies.
  • •Rated CVSS 6.3 (medium) by Strix.Ai citing the CNA advisory; NVD analysis was pending at publication.
  • •A public proof-of-concept harness exists, but no in-the-wild exploitation is reported in the articles.

CVE-2026-107853 affects the three-argument xOnlyPointAddTweakCheck path in tiny-secp256k1 from 2.1.0 through 2.2.4 and in @bitcoin-js/tiny-secp256k1-asmjs from 2.2.2 through 2.2.4, per Strix.Ai's summary of the CNA advisory. The wasm backend's failure return from xOnlyPointAddTweak is ignored when a tweak produces the point at infinity. The shared X_ONLY_PUBLIC_KEY_INPUT buffer then still holds the original point, so a caller-supplied resultToCheck equal to that point can make the comparison return true for a derivation that does not exist. Sploitus publishes a proof-of-concept harness using the input G with tweak n−1, which lands on the point at infinity, and the harness differs only in npm package version (2.2.4 vulnerable, 2.2.5 fixed). Strix.Ai states the issue is rated CVSS 6.3 and that protocols relying on this helper to validate caller-controlled keys, tweaks, and comparison values could accept an invalid derived key. The fix in version 2.2.5 (commit ba1af1fc, GHSA-hj9c-qx2w-g7mh) removes the wasm throw paths so failures return proper codes. NVD analysis was pending per the Strix.Ai article.

Start a free Starter trial for enhanced analysis

Ask AI about this cluster

Timeline

2026-11-17
CVE-2026-107853 published
Disclosed affecting tiny-secp256k1 2.1.0 to 2.2.4 and the asmjs variant 2.2.2 to 2.2.4; rated CVSS 6.3.
Strix.Ai
2026-11-22
Proof-of-concept harness published
Sploitus lists a validated lab with vulnerable 2.2.4 and fixed 2.2.5 builds, using xOnlyPointAddTweakCheck(G, n−1, G) as the trigger.
Sploitus

More articles in this cluster (2)

Following this threat?

Track CVE-2026-107845 in your own feed — you're alerted when they show up in new reporting, leak sites or exploitation.

Free account · no card needed

Common questions

Which versions are affected?
tiny-secp256k1 2.1.0 through 2.2.4 and @bitcoin-js/tiny-secp256k1-asmjs 2.2.2 through 2.2.4 are affected. Version 2.2.5 contains the fix.
Is this being exploited?
The articles describe a public proof-of-concept but report no confirmed exploitation in the wild.
What should we do first?
Upgrade to tiny-secp256k1 2.2.5 (or the asmjs fixed release) and review any protocol logic that relies on xOnlyPointAddTweakCheck to validate caller-supplied keys.