cve.bz

CVE-2026-109971

4.7 mediumEPSS 0.2%

Medium (4.7). EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
A flaw was found in the clevis PKCS#11 pin. The clevis-decrypt-pkcs11 script passes the PKCS#11 token PIN as a command-line argument to pkcs11-tool, making it visible to any local user through process listing or the /proc filesystem.

Severity

CVSS 3.1

4.7 medium
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
EPSS
0.2% (unchanged from 0.2% a week ago; 0.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 5th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-10-14. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-214 Invocation of Process Using Visible Sensitive Information
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain 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.

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13clevisno fix listedDEBIAN-CVE-2026-109971
Debian14clevis24-1DEBIAN-CVE-2026-109971
Ubuntu18.04:LTS, 20.04:LTS, 22.04:LTS and 3 moreclevisno fix listedUBUNTU-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

Red Hat rates this Moderate.

Red Hat's statement

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.

Red Hat's mitigation

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.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10clevisAffected
Red Hat Enterprise Linux 7clevisFix deferred
Red Hat Enterprise Linux 8clevisFix deferred
Red Hat Enterprise Linux 9clevisAffected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-8Not affected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-9Not affected
Red Hat OpenShift Container Platform 5openshift/ose-rhel-coreos-9Not 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.

References

Check your stackJSON