# CVE-2026-41054: Missing exit out of permission check in haveged could lead to root exploit

> Local unprivileged users can execute privileged commands due to a missing exit in the haveged daemon's permission check, leading to root privilege escalation.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 20 May 2026
- **Updated:** 5 Jun 2026
- **Also known as:** ALPINE-CVE-2026-41054, AZL-87113, BELL-CVE-2026-41054, DEBIAN-CVE-2026-41054, GHSA-c5g3-m8p9-m3gh, MGASA-2026-0275, SUSE-SU-2026:2008-1, SUSE-SU-2026:2009-1, UBUNTU-CVE-2026-41054, USN-8358-1, openSUSE-SU-2026:10833-1, openSUSE-SU-2026:21958-1

## What is CVE-2026-41054?

CVE-2026-41054 is a high-severity authentication bypass vulnerability in Container suse/sle-micro-rancher/5.3:latest, published on 20 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In `src/havegecmd.c`, the `socket_handler` function performs a credential check on the abstract UNIX socket (`\0/sys/entropy/haveged`). However, while it detects if the connecting user is not root (`cred.uid != 0`) and prepares a negative acknowledgement (`ASCII_NAK`), it **fails to stop execution**. The code proceeds to the `switch` statement, allowing any local unprivileged user to execute privileged commands such as `MAGIC_CHROOT`.

Weakness: CWE-305 (Authentication Bypass by Primary Weakness)

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `haveged` | openSUSE:Leap 16.0 | All versions | 1.9.19-bp160.2.1 |
| `haveged` | openSUSE:Tumbleweed | All versions | 1.9.21-1.1 |

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

Apply the vendor's patch.

## Is CVE-2026-41054 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-41054 is a high-severity authentication bypass vulnerability in Container suse/sle-micro-rancher/5.3:latest, published on 20 May 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-41054 in the wild and no public exploit code.

Affected product: Container suse/sle-micro-rancher/5.3:latest. 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-41054/ (Markdown: https://insights.sbomify.com/CVE-2026-41054/index.md)
```

## Sources

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

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