Investigate in your agent.

Turn this advisory into a focused investigation. Ask your agent to check your project’s versions, explain the evidence, and suggest a compatible fix.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

Skip to content
Check your stack
CVE-2026-109971medium4.7

Clevis: clevis: pkcs#11 token pin exposed on command line via pkcs11-tool

Impact

A flaw in Clevis exposes the PKCS#11 token PIN on the command line via pkcs11-tool, making it visible to local users. The issue affects Red Hat Enterprise Linux 7, 8, 9, and 10. Local access is required to exploit the weakness.

Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.

What to do

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.

redhat guidance

Affected packages

This source has no supported package-version data for matching. You can read the advisory here, but this record alone cannot power a dependency check.

Affected products

Vendor version evidence. Product records are separate from automatic dependency matching.

Red Hat · redhat

Red Hat Enterprise Linux 10

0 ranges

Compare with this publisher’s ranges. This does not inspect your installation.

affected

unaffected

unknown

Other versions: affected

Product identifiers (CPE)cpe:/o:redhat:enterprise_linux:10

Red Hat · redhat

Red Hat Enterprise Linux 7

0 ranges

Compare with this publisher’s ranges. This does not inspect your installation.

affected

unaffected

unknown

Other versions: affected

Product identifiers (CPE)cpe:/o:redhat:enterprise_linux:7

Red Hat · redhat

Red Hat Enterprise Linux 8

0 ranges

Compare with this publisher’s ranges. This does not inspect your installation.

affected

unaffected

unknown

Other versions: affected

Product identifiers (CPE)cpe:/o:redhat:enterprise_linux:8

Red Hat · redhat

Red Hat Enterprise Linux 9

0 ranges

Compare with this publisher’s ranges. This does not inspect your installation.

affected

unaffected

unknown

Other versions: affected

Product identifiers (CPE)cpe:/o:redhat:enterprise_linux:9

Red Hat · redhat

Red Hat OpenShift Container Platform 4

0 ranges

Compare with this publisher’s ranges. This does not inspect your installation.

affected

unaffected

unknown

Other versions: unaffected

Product identifiers (CPE)cpe:/a:redhat:openshift:4

Red Hat · redhat

Red Hat OpenShift Container Platform 4

0 ranges

Compare with this publisher’s ranges. This does not inspect your installation.

affected

unaffected

unknown

Other versions: unaffected

Product identifiers (CPE)cpe:/a:redhat:openshift:4

Red Hat · redhat

Red Hat OpenShift Container Platform 5

0 ranges

Compare with this publisher’s ranges. This does not inspect your installation.

affected

unaffected

unknown

Other versions: unaffected

Product identifiers (CPE)cpe:/a:redhat:openshift:5

Original source description

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.

Inside the record

Evidence available

Package identity · not supplied
Version evidence · not supplied
Remediation guidance
Weakness classification
Additional publishers

Describes the evidence in this view, not whether the product is safe.

Original records

CVE-2026-109971

View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.

cve.new JSON →

Underlying weaknesses

The source’s classification of what caused the vulnerability.

CWE-214 ↗

Invocation of Process Using Visible Sensitive Information

redhat

Related →
Contributing organizations · 2
redhat

Assigning organization

2026-10-30
CISA-ADP

Additional data publisher

2026-10-14

What changed

Follow changes
No substantive changes have been recorded here yet. History starts when cve.new observes a change after tracking is enabled; earlier edits are not reconstructed.

Large field values are marked as truncated previews. Original source snapshots remain retained.

References

2 sources