# CVE-2026-109968: Clevis: clevis: pkcs#11 luks passphrase logged in plaintext to world-readable file

> A local attacker can read world-readable log files to obtain plaintext LUKS disk encryption passphrases due to insecure logging in the clevis PKCS#11 pin.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-109968, GHSA-6vx7-48w5-wghp, UBUNTU-CVE-2026-109968

## What is CVE-2026-109968?

CVE-2026-109968 is a medium-severity vulnerability in Red Hat Enterprise Linux 10, published on 14 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A flaw was found in the clevis PKCS#11 pin. The clevis-pkcs11-afunix-socket-unlock daemon logs LUKS disk encryption passphrases in plaintext to a log file. The log file is created without restrictive permissions, making it world-readable under the default process umask. A local attacker can read the log file to obtain the LUKS passphrase.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2026-109968?


## How do I fix CVE-2026-109968?

Apply the vendor's patch.

## Is CVE-2026-109968 being exploited?

There is no known exploitation of CVE-2026-109968 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-109968 and fix it if it is affected.

What it is: CVE-2026-109968 is a medium-severity vulnerability in Red Hat Enterprise Linux 10, published on 14 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-109968 in the wild and no public exploit code.

Affected product: Red Hat Enterprise Linux 10. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-109968/ (Markdown: https://insights.sbomify.com/CVE-2026-109968/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-109968
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-109968
- OSV: https://osv.dev/vulnerability/CVE-2026-109968

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-109968/
Summaries are generated and may contain mistakes; the official description above is the record.