CVE-2026-115407
Eclipse Foundation message forgery and decryption via GCM nonce handling
A remote attacker can forge messages and read encrypted data by causing AES-GCM nonce reuse.
Texto original en inglés · Ver en español
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
Fuente: CNA
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Divulgación | Publicada | CVE-2026-115407 divulgada · CVSS 9.1 (CNA) | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Fuente: NIST NVD | Registro visto por primera vez en NIST NVD | |
| Divulgación | Evaluación SSVC | CISA-ADP · explotación PoC pública | |
| Divulgación | Modificada | Última actualización del registro | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
Several Go modules for the crypto11 library are affected, including github.com/eclipse-keypont/crypto11/v2 from the Eclipse Foundation and the older ThalesGroup and ThalesIgnite crypto11 module paths. Remotely, without logging in or any user action, an attacker can forge messages and read encrypted data, because the library does not check GCM nonce length and can end up reusing the same IV.
Descripción original del registro (eclipse)
In `github.com/eclipse-keypont/crypto11/v2` versions `<= 2.0.0-rc8` (and the deprecated v1 module paths `github.com/eclipse-keypont/crypto11 <= 1.6.8`, `github.com/ThalesGroup/crypto11 <= 1.7.0-rc1` and `github.com/ThalesIgnite/crypto11 <= 1.2.5`), the `cipher.AEAD` returned by `SecretKey.NewGCM()` passes whatever nonce it is given straight to `CK_GCM_PARAMS` without checking its length against `NonceSize()`, and accepts an empty nonce. On a token that accepts a zero-length GCM IV — SoftHSM2 does — every `Seal` with an empty nonce encrypts under the same IV, reusing the keystream and exposing the GHASH authentication key, which allows forgeries. Separately, `Config.UseGCMIVFromHSM` sends a NULL IV with length zero to the token unless `GCMIVFromHSMControl.SupplyIvForHSMGCMEncrypt` is also set, so the token has nowhere to write the IV it generates: a `Seal` with a non-empty nonce panics after the plaintext has already been encrypted, and a `Seal` with an empty nonce returns ciphertext under an empty IV without error. On the v1 line HSM-IV mode additionally never copies the token-generated IV back to the caller, so the caller keeps its own nonce while the data was encrypted under another one.
Condiciones y alcance
Desglose de métricas
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
Gogithub.com/eclipse-keypont/crypto11/v2 |
Sin parche | — | — | — |
Gogithub.com/eclipse-keypont/crypto11 |
Sin parche | — | — | — |
Gogithub.com/ThalesGroup/crypto11 |
Sin parche | — | — | — |
Gogithub.com/ThalesIgnite/crypto11 |
Sin parche | — | — | — |
Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://github.com/eclipse-keypont/crypto11/security/advisories/GHSA-c2cp-4qw8-q4jghttps://gitlab.eclipse.org/security/cve-assignment/-/work_items/491https://github.com/eclipse-keypont/crypto11/commit/8d99b73c721c173ad85c0ca4e063c3da360a611dLas referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
