In `src/havegecmd.c`, the `socket_handler` function performs a credential check on the abstract...
Summary
Vulnerability reported (CVE-2026-41054). Successful exploitation can lead to full system takeover. Exploitable via socket_handler.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-41054 has been found.
Attackers can target a specific entry point like socket_handler over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 7.8/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "CVE-2026-41054" on the vendor's site.
CVE-2026-41054 — CWE-305 / CVSS v3 7.8
Attack vector: local / no user interaction
Attack surface: socket_handler / ASCII_NAK / switch / MAGIC_CHROOT
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-305) has been reported. Attackers reach the vulnerable code path via socket_handler.
Check the vendor advisory for the affected versions. Attack surface: socket_handler / ASCII_NAK / switch / MAGIC_CHROOT.
Severity: High (CVSS 7.8/10). Successful exploitation can lead to full system takeover.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで影響コンポーネントを特定する。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Alpine Linux ALPINE-CVE-2026-41054 haveged Fixed in: 1.9.21-r0
- BellSoft Alpaquita BELL-CVE-2026-41054 haveged Fixed in: 1.9.21-r0
- Debian DEBIAN-CVE-2026-41054 haveged Fixed in: 1.9.14-1+deb11u1
- Ubuntu UBUNTU-CVE-2026-41054 haveged
References
- web meissner@suse.de
- web openwall.com
- web openwall.com
- web openwall.com
- web openwall.com
- web nvd.nist.gov
- web github.com
- web openwall.com
- web openwall.com
- web lists.debian.org