Review reviewHigh

CVE-2026-41054

SUSE Container suse/sle-micro-rancher/5.3:latest, Container suse/sle-micro-rancher/5.4:latest, Container suse/sle-micro/5.5:latest

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`.

CVSS
7.8
EPSS
0.18%
8.29% percentile
CISA KEV
Not listed
Published
2026.05.20
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.18%
Technical severityCVSS 7.8

Vulnerability overview

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`.

Affected product and versions

Product
SUSE Container suse/sle-micro-rancher/5.3:latest, Container suse/sle-micro-rancher/5.4:latest, Container suse/sle-micro/5.5:latest
Affected versions
>= ? < 1.9.14-150400.3.11.1, >= ? < 1.9.14-150600.11.6.1
Fixed versions
No verified fixed-version field is available yet

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that SUSE Container suse/sle-micro-rancher/5.3:latest, Container suse/sle-micro-rancher/5.4:latest, Container suse/sle-micro/5.5:latest and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
CWE-305