Skip to main content
CVE-2026-115409VulnerabilityPublished

In github.com/eclipse-keypont/crypto11/v2 versions <= 2.0.0-rc8 (and the deprecated v1 module paths

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-115409· Medium 6.5

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

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (eclipse)CVSS 3.16.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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
Eclipse KeyPontgithub.com/eclipse-keypont/crypto11/v2Affected
  • <2.0.0-rc9
Fixed in
  • 2.0.0-rc9
Eclipse KeyPontgithub.com/eclipse-keypont/crypto11Affected
  • <=1.6.8
Fixed in–
Eclipse KeyPontgithub.com/ThalesGroup/crypto11Affected
  • <=1.7.0-rc1
Fixed in–
Eclipse KeyPontgithub.com/ThalesIgnite/crypto11Affected
  • <=1.2.5
Fixed in–
Gogithub.com/eclipse-keypont/crypto11/v2pkg:golang/github.com/eclipse-keypont/crypto11/v2Other threatsAffected
  • <2.0.0-rc9
Fixed in
  • 2.0.0-rc9
Gogithub.com/eclipse-keypont/crypto11pkg:golang/github.com/eclipse-keypont/crypto11Other threatsAffected
  • <=1.6.8
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

Community reviews

Loading reviews…