VulnerabilityPublished 4 Nov 2026

CVE-2026-108985: libnfs security update

Affects libnfsSource GCVE Database

Compare

Authoritative record:CVE-2026-108985· High 7.1

Not known to be exploited · CVSS 7.1 High : upgrade to 5.0.2-4.oe2403sp1 soon.

Data as of 4 Nov 2026, 16:46 UTC

CVSS 3.1 base score

7.1High

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

Patch: Available – fixed in 5.0.2-4.oe2403sp1

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: None
Integrity: Low
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: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
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: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on 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 12 Oct 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 4 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

Upgrade libnfs to 5.0.2-4.oe2403sp1.

Affected software

Product	Affected	Fixed in
openEuler 24.03-LTS-SP1libnfs`pkg:rpm/openEuler/libnfs&distro=openEuler-24.03-LTS-SP1`Other threats	Affected <5.0.2-4.oe2403sp1	Fixed in 5.0.2-4.oe2403sp1

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

AI-suggested

A patch is available and should be applied by upgrading libnfs to version 5.0.2-4.oe2403sp1 or later. No additional mitigation steps are indicated by the vendor advisory.

Description

A high-severity vulnerability (CVE-2026-108985) exists in libnfs versions prior to 5.0.2-4.oe2403sp1. The flaw is an out-of-bounds write in the ZDR decoding functionality related to lib/libnfs-zdr.c, where the maxsize parameter supplied by the caller is not properly enforced. This can lead to integrity loss and denial of service. A patch fixing this issue is available in version 5.0.2-4.oe2403sp1.

Impact

The vulnerability allows an attacker to cause an out-of-bounds write, potentially leading to denial of service or integrity issues in applications using libnfs for NFS protocol access. The CVSS score of 7.1 reflects a high severity impact primarily affecting availability and integrity. Exploitation requires network access and user interaction but no privileges.

Summary

CVE-2026-108985 affects libnfs, a library for accessing NFSv2 and NFSv3 servers from user space. The vulnerability is an out-of-bounds write in the ZDR decoding code (lib/libnfs-zdr.c) involving functions libnfs_zdr_bytes(), libnfs_zdr_string(), and libnfs_zdr_array(). The root cause is that the caller-supplied maxsize value is not honored, allowing writes beyond intended buffer boundaries. This flaw impacts versions before 5.0.2-4.oe2403sp1. The vulnerability has a CVSS 3.1 score of 7.1, indicating high severity with network attack vector, low attack complexity, no privileges required, user interaction required, unchanged scope, no confidentiality impact, limited integrity impact, and high availability impact. No known exploits in the wild have been reported. The issue is fixed in libnfs version 5.0.2-4.oe2403sp1.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 4 Nov 2026, 16:46 UTC

Technical details

References

Community reviews

Related threats