PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-109971 Red Hat CVE debrief

A flaw in the clevis PKCS#11 pin exposes the PKCS#11 token PIN on the command line via pkcs11-tool, making it visible to local users through process listing or the /proc filesystem. This vulnerability affects clevis users with encrypted data, allowing local users to access sensitive information. Defenders and administrators should assess exposure and prioritize mitigation to protect encrypted data. The CVE record and source item provide details about the vulnerability, but do not specify affected versions or remediation steps.

Vendor
Red Hat
Product
Red Hat Enterprise Linux 10
CVSS
MEDIUM 4.7
CISA KEV
Not listed in stored evidence
Original CVE published
2026-10-14
Original CVE updated
2026-10-14
Advisory published
2026-10-14
Advisory updated
2026-10-14

Who should care

Defenders and administrators of systems using clevis for encrypted data should assess exposure and prioritize mitigation to protect encrypted data. This includes verifying and mitigating the vulnerability in local systems, especially where clevis is used for encrypted data. The vulnerability allows local users to access sensitive information through process listing or the /proc filesystem.

Why it matters

This vulnerability exposes sensitive data to local users, requiring defenders to verify and mitigate the issue to protect encrypted data.

  • Local users may access sensitive data through process listing or /proc filesystem
  • Defenders must verify and mitigate this vulnerability to protect sensitive data

Technical summary

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. This vulnerability affects clevis users with encrypted data, allowing local users to access sensitive information. The vulnerability has a CVSS score of 4.7 and a severity of MEDIUM.

Defensive priority

Defenders should prioritize verifying and mitigating this vulnerability in their local systems, especially where clevis is used for encrypted data.

Recommended defensive actions

  • Verify clevis installation and usage in your environment
  • Assess local exposure to the vulnerability
  • Consider mitigating controls for sensitive data

Evidence notes

The CVE record and source item provide details about the vulnerability, but do not specify affected versions or remediation steps. The vulnerability allows local users to access sensitive information through process listing or the /proc filesystem. Defenders should verify and mitigate this vulnerability in their local systems, especially where clevis is used for encrypted data. The vulnerability has a CVSS score of 4.7 and a severity of MEDIUM.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-109971 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-109971

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-109971 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-109971

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.