In github.com/eclipse-keypont/crypto11/v2 versions <= 2.0.0-rc8 (and the deprecated v1 module paths github.com/eclipse-keypont/crypto11 <=…
CVE-2026-115409
In github.com/eclipse-keypont/crypto11/v2 versions <= 2.0.0-rc8 (and the deprecated v1 module paths github.com/eclipse-keypont/crypto11 <= 1.6.8, github.com/ThalesGroup/crypto11 <= 1.7.0-rc1 and github.com/ThalesIgnite/crypto11 <= 1.2.5), the key-pair and certificate lookup functions (FindKeyPair, FindKeyPairs, FindKeyPairsWithAttributes, FindAllKeyPairs, the FindRSAKeyPair family and FindAllPairedCertificates) pair a private key with a public key object, or with a certificate, by CKAID/CKALABEL alone, take the first match the token returns, and never verify that it belongs to the private key. PKCS#11 permits a session that has not logged in to create public token objects, so anyone able to open a session on the token — without the PIN — can plant a public key or certificate carrying a victim key's CKAID and label, and crypto11 may return it as that key's public half. An application that publishes or trusts Signer.Public() (a JWKS endpoint, a key registry, authorizedkeys, a CSR) then publishes the attacker's key, and relying parties accept anything the attacker signs as coming from the service. On the v1 line the lookup also falls back to a class-and-key-type-only search when the…
Assessment
- CVSS
- 6.5 (v3.1)
- Severity
- Medium
- Known exploited
- Not listed in CISA KEV
- Exploit availability
- Nothing found in Exploit-DB, Metasploit, Nuclei or public PoC repositories
- Published
- 20 November 2026
- Last updated
- 20 November 2026
- Affected
- Eclipse Foundation · Eclipse KeyPont
- Assigner
- eclipse
CVSS vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N
At the source
References
- https://github.com/eclipse-keypont/crypto11/security/advisories/GHSA-2xw8-72pq-h8wg
- https://github.com/eclipse-keypont/crypto11/commit/8d99b73c721c173ad85c0ca4e063c3da360a611d
- https://gitlab.eclipse.org/security/cve-assignment/-/work_items/489
- https://github.com/eclipse-keypont/crypto11/releases/tag/v2.0.0-rc9
Community proofs of concept
No community proof of concept yet. If you have one for a published vulnerability and the right to share it, add it below — it will appear here once reviewed.
Submit a proof of concept
Only for publicly disclosed vulnerabilities, and only material from testing you were authorised to perform. This platform does not buy, sell, or broker exploits — see earning from vulnerability research for legitimate bounty programs. Submissions are reviewed before they appear. Text only; do not include live credentials, personal data, or anything targeting systems you are not permitted to test.
Query this programmatically
Agents can read this through the MCP endpoint, or over HTTP:
curl https://cve.zerocrew.in/api/cve/CVE-2026-115409