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

Published Nov 17, 2026
·
Updated

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 XONLYPUBLICKEYINPUT 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.

Affected Software

2 affected components
npm/tiny-secp256k1>=2.1.0<2.2.5
npm/@bitcoin-js/tiny-secp256k1-asmjs>=2.2.2<2.2.5

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade npm/tiny-secp256k1 to a version that resolves this vulnerability.

    Fixed in 2.2.5
  2. Upgrade

    Upgrade npm/@bitcoin-js/tiny-secp256k1-asmjs to a version that resolves this vulnerability.

    Fixed in 2.2.5

Event History

Nov 17, 2026
CVE Published
via MITRE·07:23 PM
Data Sourced
via OSV·07:23 PM
DescriptionSeverityWeakness
Data Sourced
via MITRE·07:23 PM
DescriptionWeakness
Data Sourced
via NVD·08:17 PM
DescriptionSeverityWeakness
Nov 18, 2026
Exploit Published
via CISA·04:41 PM

Frequently Asked Questions

1

Which package versions need remediation?

tiny-secp256k1 is affected from 2.1.0 through versions before 2.2.5. @bitcoin-js/tiny-secp256k1-asmjs is affected from 2.2.2 through versions before 2.2.5; version 2.2.5 fixes the issue.

2

What inputs must an attacker control to trigger the validation bypass?

The affected three-argument xOnlyPointAddTweakCheck path must process a tweak that produces the point at infinity. The attacker also needs to supply a resultToCheck equal to the original internal point left in the shared buffer.

3

How can we determine whether our application is exposed?

Check whether an affected package version is installed and whether the application uses the three-argument xOnlyPointAddTweakCheck helper to validate caller-controlled internal keys, tweaks, and comparison values. Protocols using that validation pattern can accept an invalid derived key.

4

What should be done if an immediate upgrade is not possible?

Do not rely on the affected helper to validate caller-controlled internal keys, tweaks, and comparison values. Ensure validation rejects tweak operations that fail because they produce the point at infinity.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203