cve.bz

CVE-2026-108985 sahlberg libnfs: Out-of-bounds Write

7.1 highEPSS 0.2%

High (7.1) in sahlberg libnfs. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
ZDR decoding in libnfs through 6.0.2 before 7613236 has an out-of-bounds write related to lib/libnfs-zdr.c with libnfs_zdr_bytes(), libnfs_zdr_string(), and libnfs_zdr_array(). The caller-supplied maxsize value is not honored.

Severity

CVSS 3.1

7.1 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:H
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 7th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-10-13. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-787 Out-of-bounds Write
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-108985 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-108985?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-108985?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-108985 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
sahlberg libnfsthrough 6.0.2

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14libnfsno fix listedDEBIAN-CVE-2026-108985
Ubuntu16.04:LTS, 18.04:LTS, 20.04:LTSlibnfsno fix listedUBUNTU-CVE-2026-108985
Ubuntu22.04:LTSlibnfs4.0.0-1ubuntu0.2UBUNTU-CVE-2026-108985 USN-9008-1
Ubuntu24.04:LTSlibnfs5.0.2-1ubuntu0.24.04.2UBUNTU-CVE-2026-108985 USN-9008-1
Ubuntu26.04:LTSlibnfs5.0.2-1ubuntu1.2UBUNTU-CVE-2026-108985 USN-9008-1
Ubuntu26.10libnfs5.0.2-1ubuntu3.1UBUNTU-CVE-2026-108985 USN-9008-1
openSUSETumbleweedlibnfs6.0.2-2.1openSUSE-SU-2026:12400-1
Azure Linux3libnfs5.0.2-3AZL-107960
Alpaquita23, 25, streamlibnfsno fix listedBELL-CVE-2026-108985

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE · Alpaquita.

Red Hat

Red Hat rates this Important.

Red Hat's statement

This vulnerability is evaluated as having an Important impact because unauthenticated remote actors can trigger out-of-bounds memory writes, leading to process crashes or potential memory corruption. In typical Red Hat environments, exposure is minimal because libnfs is not distributed in core Red Hat Enterprise Linux releases and is maintained only in community channels. Successful exploitation depends on a client application connecting to a rogue or compromised NFS server that delivers malformed RPC data.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-108985.

References

Check your stackJSON