CVE-2026-94640VulnerabilityPublished 22 Sep 2026Updated 17 Oct 2026

rpcbind. This vulnerability

Affects rpcbindSource GCVE Database

Compare

Authoritative record:CVE-2026-94640· High 7.5

Not known to be exploited · CVSS 7.5 High.

Data as of 8 Nov 2026, 23:24 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (redhat)	CVSS 3.1	7.5

EPSS: 0.6% chance of exploitation in 30 days – higher than 50% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 22 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 8 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Ubuntu 26.10rpcbind`pkg:deb/ubuntu/rpcbind?arch=source&distro=stonking`Other threats	Affected =1.2.7-1build2	Fixed in–
Ubuntu 26.04 LTSrpcbind`pkg:deb/ubuntu/rpcbind?arch=source&distro=resolute`Other threats	Affected =1.2.7-1build1 =1.2.7-1build2	Fixed in–
Ubuntu 24.04 LTSrpcbind`pkg:deb/ubuntu/rpcbind?arch=source&distro=noble`Other threats	Affected 1.2.6-6 – 1.2.6-7ubuntu2 5 affected builds	Fixed in–
Ubuntu 22.04 LTSrpcbind`pkg:deb/ubuntu/rpcbind?arch=source&distro=jammy`Other threats	Affected =1.2.5-9build1 =1.2.6-2 =1.2.6-2build1	Fixed in–
Ubuntu 20.04 LTSrpcbind`pkg:deb/ubuntu/rpcbind?arch=source&distro=focal`Other threats	Affected =1.2.5-6 =1.2.5-8	Fixed in–
Ubuntu 18.04 LTSrpcbind`pkg:deb/ubuntu/rpcbind?arch=source&distro=bionic`Other threats	Affected 0.2.3-0.6 – 0.2.3-0.6ubuntu0.18.04.4 5 affected builds	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

A vulnerability in rpcbind allows a remote, unauthenticated attacker to cause a Denial of Service (DoS) by sending many unique RPC requests. The service records these requests in unbounded in-memory lists, causing persistent memory growth and increased CPU usage, which can degrade or exhaust service availability.

Impact

The vulnerability leads to a high-severity Denial of Service impact by exhausting memory and CPU resources on the affected system, potentially rendering the rpcbind service unavailable. There is no impact on confidentiality or integrity reported.

Summary

The rpcbind service has a flaw where it maintains unbounded in-memory lists of previously unseen RPC statistics. An attacker can exploit this by sending a large number of unique RPC requests remotely without authentication, leading to memory exhaustion and high CPU consumption. This results in a Denial of Service condition, impacting the availability of the rpcbind service.

References

Community reviews

Loading reviews…