JuneAndGreen sm-crypto up to 0.3.13 Private Key data authenticity

Summaryinfo

A vulnerability classified as problematic has been found in JuneAndGreen sm-crypto up to 0.3.13. This impacts an unknown function of the component Private Key Handler. Performing a manipulation results in data authenticity. This vulnerability is known as CVE-2026-23966. Remote exploitation of the attack is possible. No exploit is available. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability was found in JuneAndGreen sm-crypto up to 0.3.13. It has been classified as problematic. This affects some unknown processing of the component Private Key Handler. The manipulation with an unknown input leads to a data authenticity vulnerability. CWE is classifying the issue as CWE-345. The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data. This is going to have an impact on confidentiality. The summary by CVE is:

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.

The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-23966 since 01/19/2026. The exploitability is told to be difficult. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available.

Upgrading to version 0.3.14 eliminates this vulnerability. Applying the patch b1c824e58fdf1eaa73692c124a095819a8c45707 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• JuneAndGreen

Name

• sm-crypto

Version

• 0.3.0
• 0.3.1
• 0.3.2
• 0.3.3
• 0.3.4
• 0.3.5
• 0.3.6
• 0.3.7
• 0.3.8
• 0.3.9
• 0.3.10
• 0.3.11
• 0.3.12
• 0.3.13

License

• open-source

Website

• Product: https://github.com/JuneAndGreen/sm-crypto/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion