Skip to main content
CVE-2026-115407VulnerabilityPublished

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-115407· Critical 9.1

Not known to be exploited · CVSS 9.1 Critical.

Data as of 20 Nov 2026, 19:47 UTC

CVSS 4.0 base score
9.1Critical
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (eclipse)CVSS 4.09.1
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA: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 20 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Eclipse Foundationgithub.com/eclipse-keypont/crypto11/v2Affected
  • <=2.0.0-rc8
Fixed in–
Eclipse Foundationgithub.com/eclipse-keypont/crypto11Affected
  • <=1.6.8
Fixed in–
Eclipse Foundationgithub.com/ThalesGroup/crypto11Affected
  • <=1.7.0-rc1
Fixed in–
Eclipse Foundationgithub.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-rc8
Fixed in–
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

Until a fix is available, users should avoid using empty nonces with the affected crypto11 versions and tokens that accept zero-length GCM IVs. Review and adjust configuration settings related to GCM IV handling (Config.UseGCMIVFromHSM and GCMIVFromHSMControl.SupplyIvForHSMGCMEncrypt) to prevent panics and unintended empty IV usage. Monitor vendor communications for updates and apply official patches once released.

Description

A critical vulnerability exists in github.com/eclipse-keypont/crypto11/v2 versions up to 2.0.0-rc8 and related deprecated v1 module paths. The issue involves improper nonce length validation in the cipher.AEAD implementation returned by SecretKey.NewGCM(), allowing empty nonces to be used. On tokens like SoftHSM2 that accept zero-length GCM IVs, this leads to keystream reuse and exposure of the GHASH authentication key, enabling forgery attacks. Additionally, configuration options related to GCM IV handling can cause panics or silent encryption under empty IVs. The v1 line also fails to copy the token-generated IV back to the caller, causing nonce mismatches during encryption.

References

Community reviews

Loading reviews…