Live › vulnerability › CVE-2026-89096
Go to dashboardnfs-utils rpc.statd leaks memory during callback processing when it receives repeated state notification requests. A remote unauthenticated attacker can grow memory use until the service degrades or crashes, causing denial of service.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Systems running nfs-utils with rpc.statd exposed to a network that untrusted parties can reach. The sources describe a remote, unauthenticated trigger, so hosts that only serve NFS on a closed internal network or do not run rpc.statd are less exposed. Machines where statd is disabled can skip it.
No product ranges from the sources yet.
rpm -q nfs-utils or dpkg -s nfs-utils to read the installed versionrpcinfo -p and ss -lntup | grep -i statdEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
A flaw was found in nfs-utils. An unauthenticated remote attacker can trigger a Denial of Service (DoS) by sending repeated state notification requests to an exposed rpc.statd service. The service fails to properly release memory allocated during callback processing, leading to continuous memory growth. Sustained requests can exhaust system resources, eventually causing the service to degrade or crash.
This page as .md · .json · in your agent: get_signal("CVE-2026-89096")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.