dbcve.org
Virtualization HostApplication · Redhat

CVE-2018-10926

HIGH · 8.8 CVSS v3.1 Published 2018-09-04
Fix available
A fix is available. Upgrade to 3.12.14 / 4.1.8 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A flaw was found in RPC request using gfs3_mknod_req supported by glusterfs server. An authenticated attacker could use this flaw to write files to an arbitrary location via path traversal and execute arbitrary code on a glusterfs server node.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A path traversal vulnerability in the gfs3_mknod_req RPC request handler in glusterfs server allows an authenticated attacker to write files to arbitrary locations on the filesystem, leading to remote code execution on affected glusterfs server nodes.

MitigationUpgrade glusterfs to a patched version and implement input validation on RPC request handlers to prevent path traversal. Consider network segmentation to limit exposure of glusterfs servers.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Virtualization HostApplication
Affected:= 4.0
Debian LinuxOperating system
Affected:= 8.0= 9.0
Enterprise LinuxOperating system
Affected:= 6.0= 7.0
Enterprise Linux ServerOperating system
Affected:= 6.0= 7.0
GlusterfsApplication
Affected:>= 3.12, < 3.12.14>= 4.1, < 4.1.8
LeapOperating system
Affected:= 15.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if glusterfs server is installed
    Run 'rpm -qa | grep glusterfs' (RHEL) or 'dpkg -l | grep glusterfs' (Debian) to list installed glusterfs packages
    Affected if glusterfs-server or glusterfs packages are installed
  2. Identify the installed glusterfs version
    Run 'gluster --version' or 'rpm -q glusterfs-server --queryformat "%VERSION"' (RHEL) / 'dpkg -s glusterfs-server | grep Version' (Debian)
    Affected if Version is 3.12.x where x < 14, OR version 4.1.x where x < 8, OR version falls between 3.12 and 4.1 without reaching these minimums
  3. Confirm the glusterfs server service is running
    Run 'systemctl status glusterd' or 'service glusterd status' to check if the glusterfs daemon (glusterd) is active
    Affected if glusterd service is running - this exposes the vulnerable RPC handler
  4. Verify if the server is listening on RPC ports
    Run 'netstat -tlnp | grep gluster' or 'ss -tlnp | grep gluster' to check if glusterfs is listening on ports 24007/tcp and related brick ports
    Affected if Glusterfs server ports are open and listening, making the vulnerable handler network-accessible
  5. Check if authentication is enforced
    Inspect '/etc/glusterfs/glusterd.vol' or run 'gluster volume info all' to see if authenticated peer relationships are required
    Affected if Server accepts connections from unauthenticated or untrusted peers - the attacker needs only valid authentication, not admin privileges

Your environment is affected if glusterfs-server is installed with version 3.12.x before 3.12.14 or 4.1.x before 4.1.8, and the glusterd service is running and network-accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to 3.12.14 / 4.1.8 or later
Fixed in 3.12.144.1.8
Interim mitigation

Upgrade glusterfs to a patched version and implement input validation on RPC request handlers to prevent path traversal. Consider network segmentation to limit exposure of glusterfs servers.

Fix this in Virtualization Host Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-10926 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-10926 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data