tiny-secp256k1 vulnerable to private key extraction when signing a malicious JSON-stringifyable message in bundled environment

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

8.1 · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:P · score source

EPSS

• CVE-2024-49364: 0.36% estimated exploitation activity in the next 30 days; percentile 30.38 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary Private key can be extracted on signing a malicious JSON-stringifiable object, when global Buffer is buffer package Details This affects only environments where require('buffer') is <https://npmjs.com/buffer E.g.: browser bundles, React Native apps, etc. Buffer.isBuffer check can be bypassed, resulting in k reuse for different messages, leading to private key extraction over a single invalid message (and a second one for which any message/signature could be taken, e.g. previously known valid one) v2.x is unaffected as it verifies input to be an actual Uint8Array instance Such a message can be constructed for any already known message/signature pair, meaning that the attack needs only a single malicious message being signed for a full key extraction While signing unverified attacker-controlled messages would be problematic itself (and exploitation of this needs such a scenario), signing a single message still should not leak the private key Also, message validation could have…

Published by the source

30 Jun 2025, 17:43 UTC

Last modified by the source

1 Jul 2025, 13:13 UTC

Source last checked

26 Oct 2026, 12:37 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-7mc2-6phr-23xc

2. Revision 2 · amended · 24 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-7mc2-6phr-23xc

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-49364

Advisory: tiny-secp256k1 vulnerable to private key extraction when signing a malicious JSON-stringifyable message in bundled environment
IDs: CVE-2024-49364, GHSA-7mc2-6phr-23xc
Record: https://patchnext.com/advisories/cve-2024-49364 (revision 3, source checked 26 Oct 2026, 12:37 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: tiny-secp256k1 1.1.7. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm tiny-secp256k1: affected <= 1.1.6; fixed in 1.1.7

## Suggested inspection (read-only)
- `npm ls tiny-secp256k1 --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on tiny-secp256k1.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-7mc2-6phr-23xc (OSV record GHSA-7mc2-6phr-23xc lists affected ranges: npm tiny-secp256k1 >=0 <1.1.7 (fixed))
- Verified: https://github.com/advisories/GHSA-7mc2-6phr-23xc (GitHub-reviewed advisory GHSA-7mc2-6phr-23xc lists affected ranges: npm tiny-secp256k1 >=0 <=1.1.6)

Commands are suggestions: review each one before running it.