CVE-2026-32614: CWE-347: Improper Verification of Cryptographic Signature in emmansun gmsm
Go ShangMi (Commercial Cryptography) Library (GMSM) is a cryptographic library that covers the Chinese commercial cryptographic public algorithms SM2/SM3/SM4/SM9/ZUC. Prior to 0.41.1, the current SM9 decryption implementation contains an infinity-point ciphertext forgery vulnerability. The root cause is that, during decryption, the elliptic-curve point C1 in the ciphertext is only deserialized and checked to be on the curve, but the implementation does not explicitly reject the point at infinity. In the current implementation, an attacker can construct C1 as the point at infinity, causing the bilinear pairing result to degenerate into the identity element in the GT group. As a result, a critical part of the key derivation input becomes a predictable constant. An attacker who only knows the target user's UID can derive the decryption key material and then forge a ciphertext that passes the integrity check. This vulnerability is fixed in 0.41.1.
AI Analysis
Technical Summary
The vulnerability CVE-2026-32614 affects the Go ShangMi (GMSM) cryptographic library, which implements Chinese commercial cryptographic algorithms including SM9. SM9 is an identity-based cryptographic scheme relying on elliptic curve cryptography and bilinear pairings. The flaw lies in the SM9 decryption process where the elliptic-curve point C1 from the ciphertext is deserialized and checked only for curve membership but not explicitly checked against being the point at infinity. The point at infinity is a special elliptic curve point that acts as the identity element for the group operation. If C1 is set to the point at infinity, the bilinear pairing operation used in key derivation degenerates to the identity element in the target group GT. This causes a critical input to the key derivation function to become a predictable constant rather than a secret value. Consequently, an attacker who knows only the victim's UID can derive the decryption key material and forge ciphertexts that pass integrity checks, effectively bypassing cryptographic protections. This compromises the integrity of encrypted messages and could allow unauthorized message injection or modification. The vulnerability is classified under CWE-347 (Improper Verification of Cryptographic Signature). The issue affects all GMSM versions prior to 0.41.1 and was publicly disclosed on March 13, 2026. The CVSS v3.1 base score is 7.5, reflecting a network attack vector, no privileges or user interaction required, and high impact on integrity but no impact on confidentiality or availability. No known exploits have been reported in the wild as of the publication date. The vulnerability is fixed in GMSM version 0.41.1 by adding explicit rejection of the point at infinity during ciphertext verification.
Potential Impact
This vulnerability undermines the integrity of cryptographic operations using the SM9 algorithm in the GMSM library. Organizations relying on GMSM for secure communications, digital signatures, or identity-based encryption may face risks of message forgery and unauthorized data manipulation. Attackers can craft malicious ciphertexts that appear valid, potentially enabling impersonation, injection of false data, or bypassing of security controls dependent on SM9. Although confidentiality is not directly impacted, the ability to forge ciphertexts can lead to trust erosion in secure communications and cryptographic protocols. The vulnerability is exploitable remotely without authentication or user interaction, increasing the risk of widespread exploitation if unpatched. Given the use of GMSM in Chinese commercial cryptography contexts, sectors such as government, finance, telecommunications, and critical infrastructure in China and regions using these cryptographic standards are particularly at risk. The lack of known exploits suggests limited immediate threat but the high severity score warrants prompt remediation to prevent future attacks.
Mitigation Recommendations
Organizations using the GMSM library should immediately upgrade to version 0.41.1 or later, which includes the fix rejecting the point at infinity during SM9 ciphertext verification. If upgrading is not immediately possible, implement additional application-level checks to validate that elliptic curve points are not the point at infinity before decryption. Conduct thorough code audits of cryptographic operations involving SM9 to ensure proper validation of all elliptic curve points and cryptographic inputs. Monitor cryptographic libraries for updates and advisories related to GMSM and SM9. Employ defense-in-depth by combining cryptographic integrity checks with application-layer message authentication codes or signatures. Educate developers and security teams on the risks of improper elliptic curve point validation and the importance of adhering to cryptographic standards. Finally, consider isolating or limiting exposure of systems using vulnerable GMSM versions until patched to reduce attack surface.
Affected Countries
China, Singapore, Malaysia, South Korea, Taiwan, Vietnam, United States, Russia, India
CVE-2026-32614: CWE-347: Improper Verification of Cryptographic Signature in emmansun gmsm
Description
Go ShangMi (Commercial Cryptography) Library (GMSM) is a cryptographic library that covers the Chinese commercial cryptographic public algorithms SM2/SM3/SM4/SM9/ZUC. Prior to 0.41.1, the current SM9 decryption implementation contains an infinity-point ciphertext forgery vulnerability. The root cause is that, during decryption, the elliptic-curve point C1 in the ciphertext is only deserialized and checked to be on the curve, but the implementation does not explicitly reject the point at infinity. In the current implementation, an attacker can construct C1 as the point at infinity, causing the bilinear pairing result to degenerate into the identity element in the GT group. As a result, a critical part of the key derivation input becomes a predictable constant. An attacker who only knows the target user's UID can derive the decryption key material and then forge a ciphertext that passes the integrity check. This vulnerability is fixed in 0.41.1.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability CVE-2026-32614 affects the Go ShangMi (GMSM) cryptographic library, which implements Chinese commercial cryptographic algorithms including SM9. SM9 is an identity-based cryptographic scheme relying on elliptic curve cryptography and bilinear pairings. The flaw lies in the SM9 decryption process where the elliptic-curve point C1 from the ciphertext is deserialized and checked only for curve membership but not explicitly checked against being the point at infinity. The point at infinity is a special elliptic curve point that acts as the identity element for the group operation. If C1 is set to the point at infinity, the bilinear pairing operation used in key derivation degenerates to the identity element in the target group GT. This causes a critical input to the key derivation function to become a predictable constant rather than a secret value. Consequently, an attacker who knows only the victim's UID can derive the decryption key material and forge ciphertexts that pass integrity checks, effectively bypassing cryptographic protections. This compromises the integrity of encrypted messages and could allow unauthorized message injection or modification. The vulnerability is classified under CWE-347 (Improper Verification of Cryptographic Signature). The issue affects all GMSM versions prior to 0.41.1 and was publicly disclosed on March 13, 2026. The CVSS v3.1 base score is 7.5, reflecting a network attack vector, no privileges or user interaction required, and high impact on integrity but no impact on confidentiality or availability. No known exploits have been reported in the wild as of the publication date. The vulnerability is fixed in GMSM version 0.41.1 by adding explicit rejection of the point at infinity during ciphertext verification.
Potential Impact
This vulnerability undermines the integrity of cryptographic operations using the SM9 algorithm in the GMSM library. Organizations relying on GMSM for secure communications, digital signatures, or identity-based encryption may face risks of message forgery and unauthorized data manipulation. Attackers can craft malicious ciphertexts that appear valid, potentially enabling impersonation, injection of false data, or bypassing of security controls dependent on SM9. Although confidentiality is not directly impacted, the ability to forge ciphertexts can lead to trust erosion in secure communications and cryptographic protocols. The vulnerability is exploitable remotely without authentication or user interaction, increasing the risk of widespread exploitation if unpatched. Given the use of GMSM in Chinese commercial cryptography contexts, sectors such as government, finance, telecommunications, and critical infrastructure in China and regions using these cryptographic standards are particularly at risk. The lack of known exploits suggests limited immediate threat but the high severity score warrants prompt remediation to prevent future attacks.
Mitigation Recommendations
Organizations using the GMSM library should immediately upgrade to version 0.41.1 or later, which includes the fix rejecting the point at infinity during SM9 ciphertext verification. If upgrading is not immediately possible, implement additional application-level checks to validate that elliptic curve points are not the point at infinity before decryption. Conduct thorough code audits of cryptographic operations involving SM9 to ensure proper validation of all elliptic curve points and cryptographic inputs. Monitor cryptographic libraries for updates and advisories related to GMSM and SM9. Employ defense-in-depth by combining cryptographic integrity checks with application-layer message authentication codes or signatures. Educate developers and security teams on the risks of improper elliptic curve point validation and the importance of adhering to cryptographic standards. Finally, consider isolating or limiting exposure of systems using vulnerable GMSM versions until patched to reduce attack surface.
Affected Countries
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-03-12T14:54:24.271Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 69b473bd2f860ef943aa93f2
Added to database: 3/13/2026, 8:29:49 PM
Last enriched: 3/20/2026, 11:20:56 PM
Last updated: 4/29/2026, 12:26:05 AM
Views: 54
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.