PT-2026-153043

CVE-2026-115407

·

Published

2026-11-20

·

Updated

2026-11-20

Description by

CVSS 4.0
9.1
Critical
MetricsAV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
Name of the Vulnerable Software and Affected Versions github.com/eclipse-keypont/crypto11/v2 versions prior to 2.0.0-rc9 github.com/eclipse-keypont/crypto11 versions prior to 1.6.9 github.com/ThalesGroup/crypto11 versions prior to 1.7.0-rc2 github.com/ThalesIgnite/crypto11 versions prior to 1.2.6
Description The cipher.AEAD returned by SecretKey.NewGCM() passes the provided nonce to CK GCM PARAMS without verifying its length against NonceSize(), allowing empty nonces. On tokens that accept zero-length GCM IVs, such as SoftHSM2, using an empty nonce results in the same IV being used for every Seal operation. This reuse of the keystream exposes the GHASH authentication key, enabling message forgery and decryption of data. Additionally, when Config.UseGCMIVFromHSM is enabled without GCMIVFromHSMControl.SupplyIvForHSMGCMEncrypt, a NULL IV with zero length is sent to the token. This causes a panic during a Seal operation if a non-empty nonce is used, or returns ciphertext under an empty IV if an empty nonce is used. In the v1 module, HSM-IV mode fails to copy the token-generated IV back to the caller, leading to a mismatch between the nonce held by the caller and the one used for encryption.
Recommendations Update github.com/eclipse-keypont/crypto11/v2 to version 2.0.0-rc9 or later. Update github.com/eclipse-keypont/crypto11 to version 1.6.9 or later. Update github.com/ThalesGroup/crypto11 to version 1.7.0-rc2 or later. Update github.com/ThalesIgnite/crypto11 to version 1.2.6 or later.
Exploitability
Exploit
Fix
Impacts
Vendors
Affected products
Related identifiers
Found an issue in the description? Have something to add? Feel free to write us 👾