9.1

CVSS Score

3.1

-

CVSS Score

Basic Information

Concerned about an active attack path?

Talk to our security experts and see Miggo in action.

Miggo Vulnerability Database

→

CVE-2026-23966

CVE-2026-23966: sm-crypto Affected by Private Key Recovery in SM2-PKE

sm-crypto provides JavaScript implementations of the Chinese cryptographic algorithms SM2, SM3, and SM4. A private key recovery vulnerability exists in the SM2 decryption logic of sm-crypto prior to version 0.3.14. By interacting with the SM2 decryption interface multiple times, an attacker can fully recover the private key within approximately several hundred interactions. Version 0.3.14 patches the issue.

(GitHub Advisory)

Miggo Vulnerability Database

→

CVE-2026-23966

CVE-2026-23966:

9.1

CVSS Score

3.1

-

CVSS Score

Basic Information

Is this CVE running in your environment?

Easily map the attack path and prioritize which CVEs are a threat to your organization

Validate Exposure

Technical Details

Package Name	Ecosystem	Vulnerable Versions	First Patched Version
sm-crypto	npm	< 0.3.14	0.3.14

Technical Details

Vulnerability Intelligence
Miggo AI

Root Cause Analysis

The vulnerability GHSA-pgx9-497m-6c4v in sm-crypto allows for private key recovery. The analysis of the fixing commit b1c824e58fdf1eaa73692c124a095819a8c45707 reveals that the doDecrypt function in src/sm2/index.js was the source of this vulnerability. It failed to validate a crucial component of the input ciphertext, a point c1 on the elliptic curve. This allowed an attacker to send crafted ciphertexts and, through repeated interactions, deduce the private key. The patch adds the necessary validation for c1. Additionally, the same commit patched the doVerifySignature function to add validation for signature components and the public key, indicating that this function was also vulnerable to potential attacks, although the primary vulnerability described is in doDecrypt.

Vulnerable functions

doDecrypt

src/sm2/index.js

The `doDecrypt` function was missing a check to validate if the point `c1` from the ciphertext is a valid point on the elliptic curve. This allowed an attacker to use an invalid point to extract information about the private key with each decryption query, eventually leading to full private key recovery. The patch adds a validation step for `c1`.

doVerifySignature

src/sm2/index.js

The function `doVerifySignature` did not properly validate the signature components `r` and `s`, and the public key. The patch adds checks to ensure that `r` and `s` are within the valid range [1, n-1], and that the public key is a valid point on the curve. Without these checks, an attacker could potentially forge a signature or cause other issues.

Vulnerability Intelligence
Miggo AI

Unlock WAF rules for this CVE

Generate vendor-ready rules for the observed attack patterns, plus reasoning and safe deployment guidance

Get WAF rules

WAF Protection Rules

WAF Rule

W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.

Reasoning

*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.