Service crash via unreleased callback memory
Published Oct 16, 2026 · Updated Oct 16, 2026
Memory leakage in nfs-utils rpc.statd allows remote attackers to crash the service through repeated state notification requests. Callback processing fails to release allocated memory, allowing sustained requests to exhaust system resources. Exploitation requires a network-exposed rpc.statd service but no authentication; the documented consequence is service degradation or a crash.
Summary
What happened
Memory leakage in nfs-utils rpc.statd allows remote attackers to crash the service through repeated state notification requests. Callback processing fails to release allocated memory, allowing sustained requests to exhaust system resources. Exploitation requires a network-exposed rpc.statd service but no authentication; the documented consequence is service degradation or a crash.
The record
- CVE
- CVE-2026-89096
- Published
- Oct 16, 2026
- Updated
- Oct 16, 2026
- Vendor
- libuser Project
- Product
- Red Hat OpenShift Container Platform 4
- Classifications
- CWE-772, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 16, 2026CVE publishedPublication date reported by the CVE source.
- Oct 16, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started