CVE-2024-48930Active Exploitation

LOWCVSS 8.7 · HIGH

Exploitation ongoing with high activity in latest observed window (1 mentions)

Immediate actions

  • Prioritize remediation for affected systems immediately
  • Assume compromise if assets are exposed
  • Track advisory updates for patch or workaround availability

Recommended action window: Immediate (within 24h)

NVD description

secp256k1-node is a Node.js binding for an Optimized C library for EC operations on curve secp256k1. In `elliptic`-based version, `loadUncompressedPublicKey` has a check that the public key is on the curve. Prior to versions 5.0.1, 4.0.4, and 3.8.1, however, `loadCompressedPublicKey` is missing that check. That allows the attacker to use public keys on low-cardinality curves to extract enough information to fully restore the private key from as little as 11 ECDH sessions, and very cheaply on compute power. Other operations on public keys are also affected, including e.g. `publicKeyVerify()` incorrectly returning `true` on those invalid keys, and e.g. `publicKeyTweakMul()` also returning predictable outcomes allowing to restore the tweak. Versions 5.0.1, 4.0.4, and 3.8.1 contain a fix for the issue.

3.5/ 10 priority

Sources & remediation

Weakness type (CWE)
CWE-354

Priority

LOW

Exploitation

ACTIVE

PoC

NONE

Patch

NONE

Momentum

NONE

Threat summary

  • Active exploitation appears in 1 classified signals
  • 1 mentions across 1 observed day

What's happening

  • Active exploitation reported across 1 signal
  • Technical details provided in 1 signal
  • 1 total mentions across 1 day

Deep dive

Activity timeline1 mentions / 1d
00111Mentions · 2026-08-09: 1Active Exploitation · 2026-08-09: 1Technical Details · 2026-08-09: 108-09
Signal classification1 categories
Active Exploitation
1100.0%
Full discourse1 post
  • Ashutosh Singh@0xAshutosh
    Active Exploitation

    Bitcoin’s cryptographic security isn’t just about whether secp256k1 is “broken.” Recent vulnerabilities show risks across the entire stack: • CVE-2024-49364 — private-key extraction • CVE-2024-48930 — ECDH private-key extraction • CVE-2023-49292 — private-key recovery • CVE-2023-39910 — weak wallet entropy • CVE-2021-38195 — invalid signature acceptance • CVE-2019-25003 — timing side channel CVE-2023-39910 (Milk Sad) was exploited in the wild, enabling recovery of vulnerable wallet private keys and theft of funds. August 2026 adds another warning: a Coldcard wallet flaw was linked to coordinated attacks reportedly draining nearly $89M from 1,000+ Bitcoin wallets. And vulnerabilities don’t always have CVEs. Reused/predictable ECDSA nonces, RNG failures, invalid-curve attacks, side channels, firmware bugs and supply-chain compromises can all threaten private keys. Bitcoin also relies on Schnorr signatures through BIP-340 and Taproot (BIP-341/342), not just ECDSA. Then there’s the long-term threat: quantum computers could eventually break the elliptic-curve cryptography securing Bitcoin. The risk isn’t that secp256k1 has suddenly been cracked. The risk is the entire security stack. Bitcoin needs continuous cryptographic auditing, secure randomness and nonce generation, hardened implementations, responsible disclosure, and a credible post-quantum migration path — before the threat becomes urgent.

    Post summary

    The article lists several Bitcoin‑related CVEs and confirms that CVE‑2023‑39910 has been actively exploited, but it offers no PoC, exploit code, or remediation details.

    00011384
    286 followersView on X

Explore more