Eclipse-keypont KeyPont up to 2.0.0-rc8 ML-KEM Key Pair Lookup data authenticity

Summaryinfo

A vulnerability described as problematic has been identified in Eclipse-keypont KeyPont up to 2.0.0-rc8. The affected element is the function FindMLKEMKeyPair/FindMLKEMKeyPairs/FindMLKEMKeyPairsWithAttributes of the component ML-KEM Key Pair Lookup. Executing a manipulation can lead to data authenticity. This vulnerability is registered as CVE-2026-115408. The attack needs to be launched locally. No exploit is available.

Detailsinfo

A vulnerability has been found in Eclipse-keypont KeyPont up to 2.0.0-rc8 and classified as problematic. This vulnerability affects the function FindMLKEMKeyPair/FindMLKEMKeyPairs/FindMLKEMKeyPairsWithAttributes of the component ML-KEM Key Pair Lookup. The manipulation with an unknown input leads to a data authenticity vulnerability. The CWE definition for the vulnerability is CWE-345. The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data. As an impact it is known to affect confidentiality. CVE summarizes:

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.

The advisory is shared for download at github.com. This vulnerability was named CVE-2026-115408 since 10/22/2026. The exploitation appears to be easy. The attack needs to be approached locally. Successful exploitation requires user interaction by the victim. There are known technical details, but no exploit is available.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Vendor

• Eclipse-keypont

Name

• KeyPont

Version

• 2.0.0-rc1
• 2.0.0-rc2
• 2.0.0-rc3
• 2.0.0-rc4
• 2.0.0-rc5
• 2.0.0-rc6
• 2.0.0-rc7
• 2.0.0-rc8

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion