# CVE-2018-10906: Security feature bypass in fuse > Attackers can bypass SELinux restrictions to mount FUSE filesystems accessible by others, potentially causing denial of service or other impacts. - **Severity:** Medium 5.3 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`) - **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:** 24 Jul 2018 - **Updated:** 5 Aug 2024 - **Also known as:** ALPINE-CVE-2018-10906, AZL-34694, AZL-6430, CVE-2021-33805, DEBIAN-CVE-2018-10906, DLA-1468-1, DSA-4257-1, GHSA-35h9-x59q-8xcf, RHSA-2018:3324, SUSE-SU-2018:3219-1, SUSE-SU-2018:3260-1, SUSE-SU-2019:13948-1, UBUNTU-CVE-2018-10906, USN-5326-1 ## What is CVE-2018-10906? CVE-2018-10906 is a medium-severity vulnerability in Debian Debian Linux, published on 24 Jul 2018. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description In fuse before versions 2.9.8 and 3.x before 3.2.5, fusermount is vulnerable to a restriction bypass when SELinux is active. This allows non-root users to mount a FUSE file system with the 'allow_other' mount option regardless of whether 'user_allow_other' is set in the fuse configuration. An attacker may use this flaw to mount a FUSE file system, accessible by other users, and trick them into accessing files on that file system, possibly causing Denial of Service or other unspecified effects. Weakness: CWE-269 (Improper Privilege Management), CWE-285 (Improper Authorization) ## Which versions are affected by CVE-2018-10906? It affects 5 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `fuse` | Red Hat:enterprise_linux:7::client | All versions | 0:2.9.2-11.el7 | | `fuse-debuginfo` | Red Hat:enterprise_linux:7::client | All versions | 0:2.9.2-11.el7 | | `fuse-devel` | Red Hat:enterprise_linux:7::client | All versions | 0:2.9.2-11.el7 | | `fuse-libs` | Red Hat:enterprise_linux:7::client | All versions | 0:2.9.2-11.el7 | | `fuse` | Red Hat:enterprise_linux:7::computenode | All versions | 0:2.9.2-11.el7 | | `fuse-debuginfo` | Red Hat:enterprise_linux:7::computenode | All versions | 0:2.9.2-11.el7 | | `fuse-devel` | Red Hat:enterprise_linux:7::computenode | All versions | 0:2.9.2-11.el7 | | `fuse-libs` | Red Hat:enterprise_linux:7::computenode | All versions | 0:2.9.2-11.el7 | | `fuse` | Red Hat:enterprise_linux:7::server | All versions | 0:2.9.2-11.el7 | | `fuse-debuginfo` | Red Hat:enterprise_linux:7::server | All versions | 0:2.9.2-11.el7 | | `fuse-devel` | Red Hat:enterprise_linux:7::server | All versions | 0:2.9.2-11.el7 | | `fuse-libs` | Red Hat:enterprise_linux:7::server | All versions | 0:2.9.2-11.el7 | | `fuse` | Red Hat:enterprise_linux:7::workstation | All versions | 0:2.9.2-11.el7 | | `fuse-debuginfo` | Red Hat:enterprise_linux:7::workstation | All versions | 0:2.9.2-11.el7 | | `fuse-devel` | Red Hat:enterprise_linux:7::workstation | All versions | 0:2.9.2-11.el7 | | `fuse-libs` | Red Hat:enterprise_linux:7::workstation | All versions | 0:2.9.2-11.el7 | | `fuse` | SUSE:Linux Enterprise Desktop 12 SP3 | All versions | 2.9.3-6.3.1 | | `fuse` | SUSE:Linux Enterprise Module for Basesystem 15 | All versions | 2.9.7-3.3.1 | | `fuse` | SUSE:Linux Enterprise Server 11 SP4 | All versions | 2.8.7-0.11.3.1 | | `fuse` | SUSE:Linux Enterprise Server 12 SP3 | All versions | 2.9.3-6.3.1 | | `fuse` | SUSE:Linux Enterprise Server for SAP Applications 11 SP4 | All versions | 2.8.7-0.11.3.1 | | `fuse` | SUSE:Linux Enterprise Server for SAP Applications 12 SP3 | All versions | 2.9.3-6.3.1 | | `fuse` | SUSE:Linux Enterprise Software Development Kit 11 SP4 | All versions | 2.8.7-0.11.3.1 | | `fuse` | SUSE:Linux Enterprise Software Development Kit 12 SP3 | All versions | 2.9.3-6.3.1 | Products: Debian Debian Linux, Fuse Project Fuse, Redhat Enterprise Linux Desktop, Redhat Enterprise Linux Server, Redhat Enterprise Linux Workstation. ## How do I fix CVE-2018-10906? Upgrade to a fixed version. ## Is CVE-2018-10906 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-10906 exists. Public exploit code: - fusermount - user_allow_other Restriction Bypass and SELinux Label Control (exploitdb) ## Other vulnerabilities in Debian Debian Linux - [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild) - [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild) - [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild) - [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild) - [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2018-10906 and fix it if it is affected. What it is: CVE-2018-10906 is a medium-severity vulnerability in Debian Debian Linux, published on 24 Jul 2018. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-10906 exists. Affected product: Debian Debian Linux. 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-2018-10906/ (Markdown: https://insights.sbomify.com/CVE-2018-10906/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2018-10906 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-10906 - OSV: https://osv.dev/vulnerability/CVE-2018-10906 --- From sbomify Insights: https://insights.sbomify.com/CVE-2018-10906/ Summaries are generated and may contain mistakes; the official description above is the record.