Skip to content
statance
MenuClose
Log inStart for free ↗
medium · CVSS 5.5

CVE-2026-89098

Nfs-utils: nfs-utils: denial of service via assertion failure in fsidd

Published 16 Oct 2026 · Source updated 6 Nov 2026 · Retrieved 2026-11-06 01:53 UTC

Monitor this CVE ↗Full CVE monitoring on Pro and Business

What happened?

A flaw was found in nfs-utils. The fsidd daemon improperly handles input received over its local domain socket by relying on program assertions to verify command arguments. A local user can exploit this vulnerability by sending a malformed request lacking the required arguments to trigger an assertion failure. This causes the daemon to crash, resulting in a Denial of Service (DoS) for filesystem identifier lookup services until restarted.

Description supplied by CVE Program. Formatting is simplified; follow the original advisory for full details.

Affected software and versions

Source-provided software and version information
SoftwareVersion informationFixed version
nfs-utilsRed HatDefault status: affectedSee vendor advisory
nfs-utilsRed HatDefault status: unknownSee vendor advisory
nfs-utilsRed HatDefault status: affectedSee vendor advisory
nfs-utilsRed HatDefault status: affectedSee vendor advisory
nfs-utilsRed HatDefault status: affectedSee vendor advisory
openshift/ose-rhel-coreos-8Red HatDefault status: affectedSee vendor advisory
openshift/ose-rhel-coreos-9Red HatDefault status: affectedSee vendor advisory
openshift/ose-rhel-coreos-9Red HatDefault status: affectedSee vendor advisory

Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.

Is it being exploited?

This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.

CISA data retrieved 2026-11-06 16:38 UTC. Check CISA ↗

How to respond

  1. Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
  2. Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
  3. Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.

Sources and remediation references

This public advisory does not determine whether a particular server is affected. Records are refreshed as sources change; verify urgent decisions against the original advisory.

← Browse the public CVE feed