In github.com/eclipse-keypont/crypto11/v2 versions <= 2.0.0-rc8 (and the deprecated v1 module paths
Source GCVE Database
Not known to be exploited · CVSS 6.5 Medium : upgrade to 2.0.0-rc9 when convenient.
Data as of 20 Nov 2026, 14:10 UTC
Thin evidence
One scorer or none| CNA (eclipse) | CVSS 3.1 | 6.5 |
|---|
- Patch
- Available – fixed in 2.0.0-rc9
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 20 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.
What to do
Upgrade Eclipse KeyPont and github.com/eclipse-keypont/crypto11/v2 to 2.0.0-rc9.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Eclipse KeyPontgithub.com/eclipse-keypont/crypto11/v2 | Affected
| Fixed in
|
| Eclipse KeyPontgithub.com/eclipse-keypont/crypto11 | Affected
| Fixed in– |
| Eclipse KeyPontgithub.com/ThalesGroup/crypto11 | Affected
| Fixed in– |
| Eclipse KeyPontgithub.com/ThalesIgnite/crypto11 | Affected
| Fixed in– |
Gogithub.com/eclipse-keypont/crypto11/v2pkg:golang/github.com/eclipse-keypont/crypto11/v2Other threats | Affected
| Fixed in
|
Gogithub.com/eclipse-keypont/crypto11pkg:golang/github.com/eclipse-keypont/crypto11Other threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Users should migrate from deprecated v1 module paths to github.com/eclipse-keypont/crypto11/v2 version 2.0.0-rc9 or later, where this issue is fixed. Restricting token session access to trusted users can reduce risk but does not fully mitigate the vulnerability.
Description
A vulnerability in github.com/eclipse-keypont/crypto11 versions up to 2.0.0-rc8 and deprecated v1 module paths allows improper pairing of private keys with public keys or certificates by CKA_ID/CKA_LABEL alone without verification. This can enable an attacker who can open a session on the token without the PIN to plant a public key or certificate that is incorrectly associated with a victim's private key. Applications that publish or trust the public key may then expose the attacker's key as legitimate, allowing signature forgery acceptance by relying parties. The deprecated v1 modules will not be fixed; users should upgrade to version 2.0.0-rc9 or later.
References
- github.com/eclipse-keypont/crypto11/security/advisories/GHSA-2xw8-72pq-h8wg (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-115409 (opens in a new tab)
- github.com/eclipse-keypont/crypto11/commit/8d99b73c721c173ad85c0ca4e063c3da360a611d (opens in a new tab)
- github.com/eclipse-keypont/crypto11/releases/tag/v2.0.0-rc9 (opens in a new tab)
- gitlab.eclipse.org/security/cve-assignment/-/work_items/489 (opens in a new tab)