Skip to content
statance
MenuClose
medium · CVSS 5.3

CVE-2026-85977

Libtirpc: libtirpc: denial of service via unbounded memory allocation during portmapper response decoding

Published 16 Oct 2026 · Source updated 6 Nov 2026 · Retrieved 2026-11-06 07:47 UTC

Monitor this CVE ↗Full CVE monitoring on Pro and Business

What happened?

A flaw was found in libtirpc. A remote attacker can exploit this vulnerability by sending specially crafted PMAPPROC_DUMP replies to a client application that uses the pmap_getmaps() function against an attacker-controlled host. This unbounded decoding can lead to excessive memory and CPU allocation, causing the client process to experience a Denial of Service (DoS) due to resource exhaustion.

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
libtirpc-mainRed Hatunaffected: 1.3.8-0.1.hum1 to < *See vendor advisory
libtirpcRed HatDefault status: affectedSee vendor advisory
libtirpcRed HatDefault status: affectedSee vendor advisory
libtirpcRed HatDefault status: affectedSee vendor advisory
libtirpcRed HatDefault status: affectedSee vendor advisory
libtirpcRed HatDefault status: affectedSee vendor advisory
rhoai/odh-mlflow-rhel9Red HatDefault status: unaffectedSee 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