CVSS 3.1
4.7 mediumCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:NMedium (4.7). EPSS 0.2% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:NExplain CVE-2026-109971 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-109971?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-109971?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-109971 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12, 13 | clevis | no fix listed | DEBIAN-CVE-2026-109971 |
| Debian | 14 | clevis | 24-1 | DEBIAN-CVE-2026-109971 |
| Ubuntu | 18.04:LTS, 20.04:LTS, 22.04:LTS and 3 more | clevis | no fix listed | UBUNTU-CVE-2026-109971 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.
Red Hat rates this Moderate.
The PKCS#11 clevis pin is an opt-in feature requiring explicit configuration (clevis luks bind pkcs11), PKCS#11 hardware, and activation of the corresponding systemd service or dracut module. Default clevis installations are not affected.
Red Hat rates this Moderate because the pkcs11-tool process is short-lived and the attacker must catch it during execution. The exposed credential is the PKCS#11 token PIN, not the LUKS passphrase directly, and exploiting the PIN additionally requires physical access to the PKCS#11 token.
No end-user mitigation is available for this issue. The PIN exposure occurs in the clevis-decrypt-pkcs11 script itself, which must be updated to pass the PIN through an environment variable instead of the command line.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 10 | clevis | Affected | |
| Red Hat Enterprise Linux 7 | clevis | Fix deferred | |
| Red Hat Enterprise Linux 8 | clevis | Fix deferred | |
| Red Hat Enterprise Linux 9 | clevis | Affected | |
| Red Hat OpenShift Container Platform 4 | openshift/ose-rhel-coreos-8 | Not affected | |
| Red Hat OpenShift Container Platform 4 | openshift/ose-rhel-coreos-9 | Not affected | |
| Red Hat OpenShift Container Platform 5 | openshift/ose-rhel-coreos-9 | Not affected |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-109971.