Live › vulnerability › CVE-2026-85231
Go to dashboardlibtirpc, the RPC library used by many Linux and Unix services, does not bound memory allocation for oversized wrapped data in RPCSEC_GSS integrity or privacy requests. An authenticated remote attacker can exhaust system memory, making the RPC service unstable or terminating it.
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 an RPC service that is configured with RPCSEC_GSS integrity or privacy, such as Kerberos-secured NFS, are exposed because the flaw sits in the wrapped-data parsing path. Hosts that run no RPC services, or only use RPCSEC_GSS with authentication only, can skip it. The sources do not name the vulnerable version range.
No product ranges from the sources yet.
rpm -q libtirpc or dpkg -s libtirpc3/etc/exports or the NFS/gssd configurationEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
A flaw was found in libtirpc. An authenticated remote attacker could exploit this vulnerability by sending oversized wrapped data requests to an RPC (Remote Procedure Call) service configured with RPCSEC_GSS (Remote Procedure Call Security-Generic Security Service) integrity or privacy. This can lead to unbounded memory allocation, resulting in a Denial of Service (DoS) by exhausting system resources and causing the service to become unstable or terminate.
This page as .md · .json · in your agent: get_signal("CVE-2026-85231")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.