Skip to main content
Menu
CVEs

Eclipse Foundation key substitution in PKCS#11 key-pair binding

CVE-2026-115409EUVD-2026-131397GHSA-GQ2F-47X5-68QFPublished , updated

6.5MediumCNA
Exploited
No known exploitation
Fix
Fixed in 2.0.0-rc9
Who is exposed
Not reported

Summary

The Eclipse KeyPont crypto11 Go packages (github.com/eclipse-keypont/crypto11/v2 and the deprecated v1 module paths) pair a private key with a public key or certificate using only the CKA_ID and label, without verifying the match. A local user with low privileges who can open a session on the token, without the PIN, can plant a public key or certificate with the victim key's ID and label, so applications that publish or trust the returned public key may accept signatures the attacker makes.

Written by a model

Original description

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.

What to do

Upgrade to a fixed version: 2.0.0-rc9.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-115409 (Unverified key-pair binding lets an unauthenticated token user substitute the public key or certificate returned for a private key), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-115409 (entry last updated 2026-11-20):
Affected:
- Go package github.com/eclipse-keypont/crypto11/v2: fixed in 2.0.0-rc9
- Go package github.com/eclipse-keypont/crypto11: through 1.6.8
- Go package github.com/ThalesGroup/crypto11: through 1.7.0-rc1
- Go package github.com/ThalesIgnite/crypto11: through 1.2.5
Fixed versions: 2.0.0-rc9.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-115409 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-115409 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (Go): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/eclipse-keypont/crypto11/security/advisories/GHSA-2xw8-72pq-h8wg
- https://github.com/eclipse-keypont/crypto11/commit/8d99b73c721c173ad85c0ca4e063c3da360a611d
- https://gitlab.eclipse.org/security/cve-assignment/-/work_items/489
- https://github.com/eclipse-keypont/crypto11/releases/tag/v2.0.0-rc9
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-115409
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-115409"}.

Affected versions

cve.now Index

17Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure?/25Unknown. No advisory context yet
  • Reach10/20Affects Go packages
  • Severity6.5/10CVSS 6.5
  • No patch0/5No signal

What would change the score

  • Would score about 72 if added to CISA KEV
  • Would score about 67 if CISA's SSVC rates exploitation active
  • Would score about 39 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 6

Questions about CVE-2026-115409

Is CVE-2026-115409 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-115409?

github.com/eclipse-keypont/crypto11/v2 (Go): before 2.0.0-rc9. github.com/eclipse-keypont/crypto11 (Go): through 1.6.8. github.com/ThalesGroup/crypto11 (Go): through 1.7.0-rc1. github.com/ThalesIgnite/crypto11 (Go): through 1.2.5.

Source: cve.now feed data

How do I fix CVE-2026-115409?

Upgrade to a fixed version: 2.0.0-rc9.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.