# CVE-2026-109969: Clevis: clevis: no authentication on pkcs#11 af_unix sockets allows key injection under permissive umask

> Local attackers can inject keys or steal LUKS passphrases via unsecured AF_UNIX sockets in Clevis when permissive umask settings are used.

- **Severity:** Medium 4.7 (`CVSS:3.1/AV:L/AC:H/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:** 19 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-109969, GHSA-w2m6-gjp4-v6hh, UBUNTU-CVE-2026-109969

## What is CVE-2026-109969?

CVE-2026-109969 is a medium-severity missing authorization 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 creates AF_UNIX sockets without explicit permission restrictions or peer credential verification. Under a permissive process umask, any local user can connect to the control socket and inject arbitrary device/key pairs, or connect to the data socket to receive LUKS passphrases.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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


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

Apply the vendor's patch.

## Is CVE-2026-109969 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-109969 is a medium-severity missing authorization 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-109969 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-109969/ (Markdown: https://insights.sbomify.com/CVE-2026-109969/index.md)
```

## Sources

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

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