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


- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 27 Oct 2026
- **Updated:** 27 Oct 2026
- **Also known as:** GHSA-7842-qc22-qh4x, GHSA-922w-gjph-r2q7

## What is CVE-2026-115408?

CVE-2026-115408 is a medium-severity vulnerability in Eclipse KeyPont, published on 27 Oct 2026. 

### Official description

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.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

## Which versions are affected by CVE-2026-115408?


## How do I fix CVE-2026-115408?

No fix has been published for CVE-2026-115408 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-115408 being exploited?

There is no known exploitation of CVE-2026-115408 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-115408 and fix it if it is affected.

What it is: CVE-2026-115408 is a medium-severity vulnerability in Eclipse KeyPont, published on 27 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-115408 in the wild and no public exploit code.

Affected product: Eclipse KeyPont. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-115408/ (Markdown: https://insights.sbomify.com/CVE-2026-115408/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-115408
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-115408
- OSV: https://osv.dev/vulnerability/CVE-2026-115408

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-115408/
Summaries are generated and may contain mistakes; the official description above is the record.