# CVE-2026-3184: Util-linux: util-linux: access control bypass due to improper hostname canonicalization > Attackers can bypass PAM host-based access controls by exploiting improper hostname canonicalization in the login utility, potentially gaining unauthorized access. - **Severity:** Low 3.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 3 Apr 2026 - **Updated:** 31 Aug 2026 - **Also known as:** AZL-81911, BELL-CVE-2026-3184, DEBIAN-CVE-2026-3184, ECHO-783b-c2ac-c763, GHSA-qp7r-5rpf-pwxg, OESA-2026-1532, OESA-2026-1533, OESA-2026-1534, OESA-2026-1535, OESA-2026-1633, OESA-2026-1634, OESA-2026-1635, OESA-2026-1636, ROOT-OS-DEBIAN-12-CVE-2026-3184, ROOT-OS-DEBIAN-13-CVE-2026-3184, SUSE-SU-2026:0803-1, SUSE-SU-2026:0856-1, SUSE-SU-2026:0857-1, SUSE-SU-2026:0982-1, SUSE-SU-2026:0987-1, SUSE-SU-2026:1370-1, SUSE-SU-2026:1406-1, SUSE-SU-2026:20664-1, SUSE-SU-2026:20714-1, UBUNTU-CVE-2026-3184, openSUSE-SU-2026:10288-1 ## What is CVE-2026-3184? CVE-2026-3184 is a low-severity authentication bypass vulnerability in Redhat Hardened Images, published on 3 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description A flaw was found in util-linux. Improper hostname canonicalization in the `login(1)` utility, when invoked with the `-h` option, can modify the supplied remote hostname before setting `PAM_RHOST`. A remote attacker could exploit this by providing a specially crafted hostname, potentially bypassing host-based Pluggable Authentication Modules (PAM) access control rules that rely on fully qualified domain names. This could lead to unauthorized access. Weakness: CWE-289 (Authentication Bypass by Alternate Name) ## Which versions are affected by CVE-2026-3184? It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `util-linux` | SUSE:Linux Enterprise Micro 5.2 | All versions | 2.36.2-150300.4.53.1 | | `util-linux` | SUSE:Linux Enterprise Micro 5.2 | All versions | 2.36.2-150300.4.58.1 | | `util-linux-systemd` | SUSE:Linux Enterprise Micro 5.2 | All versions | 2.36.2-150300.4.53.1 | | `util-linux-systemd` | SUSE:Linux Enterprise Micro 5.2 | All versions | 2.36.2-150300.4.58.1 | | `util-linux` | SUSE:Linux Enterprise Micro 5.3 | All versions | 2.37.2-150400.8.41.1 | | `util-linux-systemd` | SUSE:Linux Enterprise Micro 5.3 | All versions | 2.37.2-150400.8.41.1 | | `util-linux` | SUSE:Linux Enterprise Micro 5.4 | All versions | 2.37.2-150400.8.41.1 | | `util-linux-systemd` | SUSE:Linux Enterprise Micro 5.4 | All versions | 2.37.2-150400.8.41.1 | | `util-linux` | SUSE:Linux Enterprise Micro 5.5 | All versions | 2.37.4-150500.9.23.1 | | `util-linux-systemd` | SUSE:Linux Enterprise Micro 5.5 | All versions | 2.37.4-150500.9.23.1 | | `util-linux` | SUSE:Linux Enterprise Module for Basesystem 15 SP7 | All versions | 2.40.4-150700.4.10.1 | | `util-linux-systemd` | SUSE:Linux Enterprise Module for Basesystem 15 SP7 | All versions | 2.40.4-150700.4.10.1 | | `util-linux-systemd` | SUSE:Linux Enterprise Module for Server Applications 15 SP7 | All versions | 2.40.4-150700.4.10.1 | | `python-libmount` | SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5 | All versions | 2.33.2-4.51.2 | | `util-linux` | SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5 | All versions | 2.33.2-4.51.1 | | `util-linux-systemd` | SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5 | All versions | 2.33.2-4.51.1 | | `util-linux` | SUSE:Linux Micro 6.0 | All versions | 2.39.3-5.1 | | `util-linux-systemd` | SUSE:Linux Micro 6.0 | All versions | 2.39.3-5.1 | | `util-linux` | SUSE:Linux Micro 6.1 | All versions | 2.40.4-slfo.1.1_4.1 | | `util-linux-systemd` | SUSE:Linux Micro 6.1 | All versions | 2.40.4-slfo.1.1_4.1 | | `python-libmount` | openSUSE:Leap 15.6 | All versions | 2.39.3-150600.4.18.1 | | `python3-libmount` | openSUSE:Leap 15.6 | All versions | 2.37.4-150500.9.23.1 | | `util-linux` | openSUSE:Leap 15.6 | All versions | 2.37.4-150500.9.23.1 | | `util-linux` | openSUSE:Leap 15.6 | All versions | 2.39.3-150600.4.18.1 | | `util-linux-systemd` | openSUSE:Leap 15.6 | All versions | 2.39.3-150600.4.18.1 | | `util-linux` | openSUSE:Tumbleweed | All versions | 2.41.3-4.1 | Products: Kernel Util-Linux, Redhat Hardened Images. ## How do I fix CVE-2026-3184? Apply the vendor's patch. ## Is CVE-2026-3184 being exploited? There is no known exploitation of CVE-2026-3184 in the wild and no public exploit code. ## Other vulnerabilities in Redhat Hardened Images - [CVE-2015-5224](https://insights.sbomify.com/CVE-2015-5224/): Race condition in n/a (critical 9.8) - [CVE-2018-7738](https://insights.sbomify.com/CVE-2018-7738/): Command injection in n/a (high 7.8) - [CVE-2016-2779](https://insights.sbomify.com/CVE-2016-2779/): Privilege escalation in n/a (high 7.8) - [CVE-2026-13595](https://insights.sbomify.com/CVE-2026-13595/): Util-linux: util-linux: heap use-after-free in libblkid nested partition probing (medium 6.8) - [CVE-2020-21583](https://insights.sbomify.com/CVE-2020-21583/): Command injection in n/a (medium 6.7) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-3184 and fix it if it is affected. What it is: CVE-2026-3184 is a low-severity authentication bypass vulnerability in Redhat Hardened Images, published on 3 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-3184 in the wild and no public exploit code. Affected product: Redhat Hardened Images. 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-3184/ (Markdown: https://insights.sbomify.com/CVE-2026-3184/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-3184 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-3184 - OSV: https://osv.dev/vulnerability/CVE-2026-3184 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-3184/ Summaries are generated and may contain mistakes; the official description above is the record.