- Veröffentlicht
- 20.11.2026 10:33
- Zuletzt geändert
- 20.11.2026
- EPSS (30 Tage)
- unbekannt
- CVSS-Vektor
- CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N
Beschreibung
Originaltext der Quelle, nicht übersetzt.
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 `CKA_ID`/`CKA_LABEL` 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 `CKA_ID` 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, `authorized_keys`, 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 private key has no `CKA_ID`, pairing a label-only private key with the first public key of its type on the token.
The v1 module paths are deprecated and will not be fixed; users should migrate to github.com/eclipse-keypont/crypto11/v2 version 2.0.0-rc9 or later.
Status beim Hersteller
Red Hat stuft seine Produktlinien ein: 5 betroffen, 3 nicht betroffen.
OpenShift Serverless
BetroffenFix zurückgestellt
openshift-serverless-1/kn-plugin-event-sender-rhel9
Red Hat Advanced Cluster Security 4
BetroffenFix zurückgestellt
advanced-cluster-security/rhacs-main-rhel8, advanced-cluster-security/rhacs-main-rhel9, advanced-cluster-security/rhacs-operator-bundle, advanced-cluster-security/rhacs-rhel8-operator, advanced-cluster-security/rhacs-rhel9-operator, advanced-cluster-security/rhacs-roxctl-rhel8, advanced-cluster-security/rhacs-roxctl-rhel9, advanced-cluster-security/rhacs-scanner-v4-rhel8, advanced-cluster-security/rhacs-scanner-v4-rhel9
Red Hat OpenShift Container Platform 4
BetroffenFix zurückgestellt
openshift4/oc-mirror-plugin-rhel9
Red Hat Trusted Artifact Signer
BetroffenFix zurückgestellt
rhtas/cosign-rhel9, rhtas/ec-rhel9, rhtas/fulcio-rhel9, rhtas/gitsign-rhel9, rhtas/model-transparency-cli-rhel9, rhtas/policy-controller-rhel9
Security Profiles Operator
BetroffenFix zurückgestellt
compliance/openshift-security-profiles-operator-bundle, compliance/openshift-security-profiles-rhel8-operator
Nicht betroffen (3)
Red Hat Hardened ImagesNicht betroffenKomponente nicht enthaltencosign, fulcio, kubernetes1.35, kubernetes1.36
Red Hat OpenShift Container Platform 4Nicht betroffenverwundbarer Code nicht enthaltencri-o, microshift, microshift-ai-model-serving, microshift-ai-model-serving-release-info, microshift-cert-manager, microshift-cert-manager-release-info, microshift-gateway-api, microshift-gateway-api-release-info, microshift-greenboot, microshift-low-latency, microshift-multus, microshift-multus-release-info, microshift-networking, microshift-observability, microshift-olm, microshift-olm-release-info, microshift-release-info, microshift-selinux, microshift-sriov, microshift-sriov-release-info, openshift, openshift-clients, openshift-clients-redistributable, openshift-hyperkube, openshift-kube-apiserver und 3 weitere
Red Hat OpenShift Container Platform 5Nicht betroffenverwundbarer Code nicht enthaltenopenshift
Weitere betroffene Pakete (4)
CVEEclipse Foundation/Eclipse KeyPont2.0.0-rc9CVE-2026-115409
CVEEclipse Foundation/Eclipse KeyPontkein Fix bekanntCVE-2026-115409
CVEEclipse Foundation/Eclipse KeyPontkein Fix bekanntCVE-2026-115409
CVEEclipse Foundation/Eclipse KeyPontkein Fix bekanntCVE-2026-115409
Empfohlene Prüfung
- Feststellen, ob und in welcher Version die betroffenen Pakete in Ihren Systemen, Images und Abhängigkeiten vorkommen.
- Wo eine Fix-Version genannt ist: aktualisieren. Wo nicht: Hersteller-Advisory und Referenzen auf Workarounds prüfen.
- Erreichbarkeit beachten: Der Angriffsweg (Lokal) ist aus dem CVSS-Vektor abgeleitet.
Diese Seite sagt nichts darüber, ob Ihre Systeme betroffen sind. Das klärt erst eine Prüfung Ihrer Versionen.
Referenzen
- github.com/eclipse-keypont/crypto11/security/advisories/GHSA-2xw8-72pq-h8wg
- github.com/eclipse-keypont/crypto11/commit/8d99b73c721c173ad85c0ca4e063c3da360a611d
- gitlab.eclipse.org/security/cve-assignment/-/work_items/489
- github.com/eclipse-keypont/crypto11/releases/tag/v2.0.0-rc9
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115409.json
- access.redhat.com/security/cve/CVE-2026-115409
- bugzilla.redhat.com/show_bug.cgi
- www.cve.org/CVERecord
- nvd.nist.gov/vuln/detail/CVE-2026-115409