In `github.com/eclipse-keypont/crypto11/v2` versions `<= 2.0.0-rc8` (and the deprecated v1 module...
🔗 CVE IDs covered (1)
📋 Description
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.
🔗 References (6)
- https://github.com/eclipse-keypont/crypto11/security/advisories/GHSA-2xw8-72pq-h8wg
- https://nvd.nist.gov/vuln/detail/CVE-2026-115409
- https://github.com/eclipse-keypont/crypto11/commit/8d99b73c721c173ad85c0ca4e063c3da360a611d
- https://github.com/eclipse-keypont/crypto11/releases/tag/v2.0.0-rc9
- https://gitlab.eclipse.org/security/cve-assignment/-/work_items/489
- https://github.com/advisories/GHSA-gq2f-47x5-68qf