CVE-2026-115409: Unverified key-pair binding lets an unauthenticated token user substitute the public key or certificate returned for a private key
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 CKAID/CKALABEL 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 CKAID 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, authorizedkeys, 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 CKAID, 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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
github.com/eclipse-keypont/crypto11/v2to a version that resolves this vulnerability.Fixed in 2.0.0-rc9
Event History
Frequently Asked Questions
Which applications are most exposed to this issue?
Applications are exposed when they use the affected lookup functions and publish or trust Signer.Public(), such as through a JWKS endpoint, key registry, authorized_keys file, or CSR. In that situation, a substituted public key can cause relying parties to accept attacker-signed data as if it came from the service.
What access does an attacker need?
The attacker needs to be able to open a session on the PKCS#11 token. They do not need the PIN if the token permits an unauthenticated session to create public token objects, as allowed by PKCS#11.
How can I determine whether my deployment is affected?
Check whether your application uses the listed key-pair or paired-certificate lookup functions and relies on the returned public key or certificate. The affected releases include crypto11/v2 through 2.0.0-rc8 and the deprecated v1 module paths through the stated versions.