CVE-2026-115409
Eclipse Foundation key substitution in PKCS#11 key-pair binding
Local users without the PIN can swap in a forged public key or certificate, so apps may trust attacker signatures.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N
Fuente: CNA
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Divulgación | Publicada | CVE-2026-115409 divulgada · CVSS 6.5 (CNA) | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
The Eclipse KeyPont crypto11 Go packages (github.com/eclipse-keypont/crypto11/v2 and the deprecated v1 module paths) pair a private key with a public key or certificate using only the CKA_ID and label, without verifying the match. A local user with low privileges who can open a session on the token, without the PIN, can plant a public key or certificate with the victim key's ID and label, so applications that publish or trust the returned public key may accept signatures the attacker makes.
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 key-pair and certificate lookup functions (`FindKeyPair`, `FindKeyPairs`, `FindKeyPairsWithAttributes`, `FindAllKeyPairs`, the `FindRSAKeyPair*` family and `FindAllPairedCertificates`) pair a private key with a public key object, or with a certificate, by `CKA_ID`/`CKA_LABEL` alone, take the first match the token returns, and never verify that it belongs to the private key. PKCS#11 permits a session that has not logged in to create public token objects, so anyone able to open a session on the token — without the PIN — can plant a public key or certificate carrying a victim key's `CKA_ID` and label, and crypto11 may return it as that key's public half. An application that publishes or trusts `Signer.Public()` (a JWKS endpoint, a key registry, `authorized_keys`, a CSR) then publishes the attacker's key, and relying parties accept anything the attacker signs as coming from the service. On the v1 line the lookup also falls back to a class-and-key-type-only search when the private key has no `CKA_ID`, pairing a label-only private key with the first public key of its type on the token. The v1 module paths are deprecated and will not be fixed; users should migrate to github.com/eclipse-keypont/crypto11/v2 version 2.0.0-rc9 or later.
Desglose de métricas
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
github.com/eclipse-keypont/crypto11/v2 |
Corregida | 2.0.0-rc9 | — | — |
2.0.0-rc9Arsenal 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-2xw8-72pq-h8wghttps://gitlab.eclipse.org/security/cve-assignment/-/work_items/489https://github.com/eclipse-keypont/crypto11/commit/8d99b73c721c173ad85c0ca4e063c3da360a611dhttps://github.com/eclipse-keypont/crypto11/releases/tag/v2.0.0-rc9Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
