Answer in brief
CVE-2026-115409 records a Medium severity (CVSS 6.5) vulnerability in Unverified key-pair binding lets an unauthenticated token user substitute the public key or certificate returned for a private key. The current sources do not mark it as known exploited. The current feed maps Eclipse Foundation/github.com/eclipse-keypont/crypto11 (generic), Eclipse Foundation/github.com/eclipse-keypont/crypto11/v2 (generic), Eclipse Foundation/github.com/ThalesGroup/crypto11 (generic), Eclipse Foundation/github.com/ThalesIgnite/crypto11 (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 6.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Eclipse Foundation/github.com/eclipse-keypont/crypto11 (generic), Eclipse Foundation/github.com/eclipse-keypont/crypto11/v2 (generic), Eclipse Foundation/github.com/ThalesGroup/crypto11 (generic), Eclipse Foundation/github.com/ThalesIgnite/crypto11 (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Eclipse Foundation/github.com/eclipse-keypont/crypto11generic | >=0 <=1.6.8 | Not reported |
| Eclipse Foundation/github.com/eclipse-keypont/crypto11/v2generic | >=0 <2.0.0-rc9 | 2.0.0-rc9 |
| Eclipse Foundation/github.com/ThalesGroup/crypto11generic | >=0 <=1.7.0-rc1 | Not reported |
| Eclipse Foundation/github.com/ThalesIgnite/crypto11generic | >=0 <=1.2.5 | Not reported |
Published upstream
Nov 20, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 20, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 20, 2026
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.
Quoted source text, attributed separately from HOL analysis.