# CVE-2026-115408: ML-KEM key-pair lookup can bind an unrelated or attacker-planted public key, exposing encapsulated shared secrets

Status: published. Published: 2026-10-27. Updated: 2026-11-04.

In `github.com/eclipse-keypont/crypto11/v2` versions `>= 2.0.0-rc3, <= 2.0.0-rc8`, the ML-KEM key-pair lookup functions (`FindMLKEMKeyPair`, `FindMLKEMKeyPairs`, `FindMLKEMKeyPairsWithAttributes`) locate the public half of an ML-KEM key pair by `CKA_ID`/`CKA_LABEL` and never verify it against the private key. In addition, the "ID only" fallback search runs even when the private key has no `CKA_ID`, so the search template reduces to the public-key class and the ML-KEM key type and the first ML-KEM public key on the token is returned. `Encapsulate()` on the resulting key pair encrypts the fresh shared secret to that key, so its owner — not the holder of the private key the caller looked up — can recover the secret. An attacker who can open an unauthenticated session on the token and plant a public `CKK_ML_KEM` object carrying the victim's `CKA_ID`/`CKA_LABEL` receives the shared secrets for encapsulations performed through the substituted key pair, compromising the confidentiality of those secrets and of everything protected by keys derived from them. The v1 module paths have no ML-KEM support and are not affected.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Eclipse Foundation / Eclipse KeyPont (crypto11): ≥ 2.0.0-rc3; ≤ 2.0.0-rc8 (affected, semver). Source: CNA: eclipse

## Severity and prioritization

- CVSS 3.1: 5.5 (medium); CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N; source: CNA: eclipse

- CVSS 3.1: 5.5 (medium); CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N; source: NVD: emo@eclipse.org

- CISA KEV: No listing in collected sources

- EPSS: 0.08% as of 2026-11-04; percentile 0.22%

- SSVC: exploitation poc; automatable no; technical impact partial; source ADP: CISA-ADP

- Weaknesses: CWE-345

## Exploit evidence

- exploit: https://github.com/eclipse-keypont/crypto11/security/advisories/GHSA-7842-qc22-qh4x (ADP: CISA-ADP)

## References

- https://github.com/eclipse-keypont/crypto11/security/advisories/GHSA-7842-qc22-qh4x (CNA: eclipse)

- https://github.com/eclipse-keypont/crypto11/commit/8d99b73c721c173ad85c0ca4e063c3da360a611d (CNA: eclipse)

- https://gitlab.eclipse.org/security/cve-assignment/-/work_items/490 (CNA: eclipse)

- https://github.com/eclipse-keypont/crypto11/security/advisories/GHSA-7842-qc22-qh4x (ADP: CISA-ADP; exploit)

- https://github.com/eclipse-keypont/crypto11/commit/8d99b73c721c173ad85c0ca4e063c3da360a611d (emo@eclipse.org)

- https://github.com/eclipse-keypont/crypto11/security/advisories/GHSA-7842-qc22-qh4x (emo@eclipse.org)

- https://gitlab.eclipse.org/security/cve-assignment/-/work_items/490 (emo@eclipse.org)

- https://github.com/eclipse-keypont/crypto11/security/advisories/GHSA-7842-qc22-qh4x (134c704f-9b21-4f2e-91b3-4a467353bcc0)

## Provenance

- CNA: eclipse: https://www.cve.org/CVERecord?id=CVE-2026-115408; retrieved 2026-11-04; source updated 2026-11-04

- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-115408; retrieved 2026-11-04; source updated 2026-11-04

- FIRST EPSS: https://api.first.org/data/v1/epss?cve=CVE-2026-115408; retrieved 2026-11-04; source updated Not reported

Revision: 4cb15c49fb95bca95b76a9108431a1e01538eeb915c387f51ddbecfbd982186b

Canonical: https://y2.dev/cve/CVE-2026-115408

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.