CVE-2026-115408: Eclipse KeyPont · Insufficient Verification of Data Authenticity
Affects Eclipse KeyPontSource CVE Database V5
Not known to be exploited · CVSS 5.5 Medium.
Data as of 27 Oct 2026, 12:27 UTC
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 27 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Eclipse KeyPontcrypto11 | Affected
| Fixed in– |
GitHubeclipse-keypont/crypto11pkg:github/eclipse-keypont/crypto11Other threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Users should avoid using affected versions (>=2.0.0-rc3 <=2.0.0-rc8) of Eclipse KeyPont. Restrict access to tokens to prevent unauthenticated sessions and unauthorized insertion of public key objects. Monitor vendor advisories for updates or official fixes. Since the vulnerability requires unauthenticated session access, controlling token access is critical.
Description
Eclipse KeyPont versions 2.0.0-rc3 through 2.0.0-rc8 contain a vulnerability in ML-KEM key-pair lookup functions where the public key is not verified against the private key. This allows an attacker with unauthenticated token access to substitute a public key and receive shared secrets intended for the legitimate private key owner, compromising confidentiality. The issue does not affect v1 module paths which lack ML-KEM support.