CVE-2026-94640

Rpcbind: unbounded memory allocation in rpcbind statistics tracking allows unauthenticated remote denial of service

  • High 7.5

Description

A flaw was found in rpcbind. This vulnerability allows a remote, unauthenticated attacker to cause a Denial of Service (DoS) by sending a large number of unique requests. The rpcbind service records previously unseen RPC (Remote Procedure Call) statistics in unbounded in-memory lists, leading to persistent memory growth and increased CPU usage. This can degrade or exhaust service availability.

Key facts

Published
22 Sep 2026
Last changed
5 Nov 2026
Assigned by
redhat
EPSS
0.64% likely to be exploited in the next 30 days, higher than 51.267% of CVEs (scores for 16 Nov 2026)
SSVC (CISA)
Exploitation: none; Automatable: yes; Technical impact: partial

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 7.5CVSS 3.1, Highfrom the CNA (redhat)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

What to do

  • Restrict network access to the `rpcbind` service on port 111 to trusted systems. This can be achieved by configuring firewall rules to limit inbound connections. For example, using `firewalld` on Red Hat Enterprise Linux: ```bash # To allow access only from a specific trusted network (e.g., 192.168.1.0/24) firewall-cmd --permanent --add-rich-rule='rule family="ipv4" source address="192.168.1.0/24" port port="111" protocol="tcp" accept' firewall-cmd --permanent --add-rich-rule='rule family="ipv4" source address="192.168.1.0/24" port port="111" protocol="udp" accept' firewall-cmd --reload ``` If `rpcbind` is only required for local services, ensure it is configured to listen only on the loopback interface or is otherwise protected from external network exposure. Applying these firewall rules will take effect immediately upon `firewall-cmd --reload` and may temporarily interrupt existing connections to `rpcbind`.CNA workaround statement

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
Red HatRed Hat Enterprise Linux 10
  • Default status: affected
  • 0:1.2.7-3.el10_2.1 up to but excluding * (unaffected)
Red HatRed Hat Enterprise Linux 8
  • Default status: affected
  • 0:1.2.5-11.el8_10 up to but excluding * (unaffected)
Red HatRed Hat Enterprise Linux 9
  • Default status: affected
  • 0:1.2.6-7.el9_8.1 up to but excluding * (unaffected)
Red HatRed Hat OpenShift Container Platform 4.22
  • Default status: affected
  • 4.22.9.8.202610241758-0 up to but excluding * (unaffected)
Red HatRed Hat Enterprise Linux 6
  • Default status: affected
Red HatRed Hat Enterprise Linux 7
  • Default status: affected
Red HatRed Hat OpenShift Container Platform 4
  • Default status: affected
Red HatRed Hat OpenShift Container Platform 5
  • Default status: affected

Timeline

  1. 26 Apr 2026 Reported to Red Hat.
  2. 22 Jul 2026 Made public.
  3. 22 Sep 2026 Published

Weakness

References