Is CVE-2026-115408 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-115408 being exploited in the wild.

How severe is CVE-2026-115408?

Medium severity, with a CVSS score of 5.5, published 27 October 2026.

Which products and versions are affected?

Eclipse KeyPont Crypto11 >=2.0.0-rc3, <=2.0.0-rc8.

How is CVE-2026-115408 attacked?

It is attacked over the network or from the adjacent network.

Am I affected by CVE-2026-115408?

Check whether you run Eclipse KeyPont Crypto11 at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-115408: Eclipse Keypont crypto11 ML-KEM key-pair lookup confusion

Q: Is there a fix for CVE-2026-115408?

Yes: fixed in 2.0.0-rc9. Until then: Always assign ML-KEM keys a unique `CKA_ID` and look them up by ID rather than by label. After `FindMLKEMKeyPair*`, run a self-test: encapsulate with an extractable session-object template, decapsulate the ciphertext with the same pair, and verify the shared secrets match. Restrict which principals can open unauthenticated sessions on the token. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-115408 attacked?

It is attacked over the network or from the adjacent network.

Q: Am I affected by CVE-2026-115408?

Check whether you run Eclipse KeyPont Crypto11 at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-115408 · Severity: medium · CVSS 5.5 · Published 2026-10-27

Eclipse Keypont crypto11 is a Go cryptographic library that interfaces with hardware security modules (HSMs). In affected versions, ML-KEM key-pair lookup functions can return an attacker-planted public key instead of the legitimate one, causing encrypted shared secrets to be sent to the attacker rather than the intended recipient. An unauthenticated attacker with session access to the token can steal all encapsulated secrets and compromise anything derived from them.

Vendors: Eclipse KeyPont.

Quick answers

Is CVE-2026-115408 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-115408 being exploited in the wild.
How severe is CVE-2026-115408?: Medium severity, with a CVSS score of 5.5, published 27 October 2026.
Which products and versions are affected?: Eclipse KeyPont Crypto11 >=2.0.0-rc3, <=2.0.0-rc8.
Is there a fix for CVE-2026-115408?: Yes: fixed in 2.0.0-rc9. Until then: Always assign ML-KEM keys a unique `CKA_ID` and look them up by ID rather than by label. After `FindMLKEMKeyPair*`, run a self-test: encapsulate with an extractable session-object template, decapsulate the ciphertext with the same pair, and verify the shared secrets match. Restrict which principals can open unauthenticated sessions on the token. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-115408 attacked?: It is attacked over the network or from the adjacent network.
Am I affected by CVE-2026-115408?: Check whether you run Eclipse KeyPont Crypto11 at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: 2.0.0-rc9

Always assign ML-KEM keys a unique `CKA_ID` and look them up by ID rather than by label. After `FindMLKEMKeyPair*`, run a self-test: encapsulate with an extractable session-object template, decapsulate the ciphertext with the same pair, and verify the shared secrets match. Restrict which principals can open unauthenticated sessions on the token.

Technical details

The ML-KEM key-pair lookup functions (`FindMLKEMKeyPair`, `FindMLKEMKeyPairs`, `FindMLKEMKeyPairsWithAttributes`) in mlkem.go locate a public key by `CKA_ID` and `CKA_LABEL` without verifying it matches the private key, and perform an "ID only" fallback search even when the private key has no `CKA_ID`, matching any ML-KEM public key on the token. An unauthenticated session can plant a public `CKK_ML_KEM` object with the victim's attributes; `Encapsulate()` on the resulting key pair then encrypts to the attacker's key instead of the legitimate public key. The fix (v2.0.0-rc9) verifies candidates via `CKA_PUBLIC_KEY_INFO` or test encapsulation/decapsulation and requires a `CKA_ID` for fallback search.

Affected products

Eclipse Keypont crypto11 >=2.0.0-rc3, <=2.0.0-rc8

Timeline

2026-10-22: disclosed
2026-10-21: patched: Fix committed 2026-10-21, released in v2.0.0-rc9

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.