# CVE-2026-53689: Integer overflow in libnfs > An integer overflow in libnfs allows attackers to cause denial of service or potentially execute code via a crafted NFS server connection. - **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:L`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 10 Jun 2026 - **Updated:** 19 Jul 2026 - **Also known as:** AZL-90153, DEBIAN-CVE-2026-53689, GHSA-379r-2p3h-m47v, MGASA-2026-0299, OESA-2026-2953, OESA-2026-2954, OESA-2026-3023, OESA-2026-3024, OESA-2026-3025, SUSE-SU-2026:22363-1, SUSE-SU-2026:22447-1, SUSE-SU-2026:2760-1, UBUNTU-CVE-2026-53689, USN-8464-1, openSUSE-SU-2026:21055-1 ## What is CVE-2026-53689? CVE-2026-53689 is a high-severity vulnerability in sahlberg libnfs, published on 10 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official description libnfs through 6.0.2 before 55c18ea does not validate a string size, leading to an integer overflow during a connection to a crafted NFS server. This occurs in libnfs_zdr_string in lib/libnfs-zdr.c. Weakness: CWE-1284 (Improper Validation of Specified Quantity in Input) ## Which versions are affected by CVE-2026-53689? | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `libnfs` | SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | All versions | 1.11.0-150000.3.3.1 | | `libnfs` | SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS | All versions | 1.11.0-150000.3.3.1 | | `libnfs` | SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS | All versions | 1.11.0-150000.3.3.1 | | `libnfs` | SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS | All versions | 1.11.0-150000.3.3.1 | | `libnfs` | SUSE:Linux Enterprise Module for Basesystem 15 SP7 | All versions | 1.11.0-150000.3.3.1 | | `libnfs` | SUSE:Linux Enterprise Module for Desktop Applications 15 SP7 | All versions | 1.11.0-150000.3.3.1 | | `libnfs` | SUSE:Linux Enterprise Server 15 SP4-LTSS | All versions | 1.11.0-150000.3.3.1 | | `libnfs` | SUSE:Linux Enterprise Server 15 SP5-LTSS | All versions | 1.11.0-150000.3.3.1 | | `libnfs` | SUSE:Linux Enterprise Server 15 SP6-LTSS | All versions | 1.11.0-150000.3.3.1 | | `libnfs` | SUSE:Linux Enterprise Server 16.0 | All versions | 5.0.3-160000.4.1 | | `libnfs` | SUSE:Linux Enterprise Server for SAP Applications 15 SP4 | All versions | 1.11.0-150000.3.3.1 | | `libnfs` | SUSE:Linux Enterprise Server for SAP Applications 15 SP5 | All versions | 1.11.0-150000.3.3.1 | | `libnfs` | SUSE:Linux Enterprise Server for SAP Applications 15 SP6 | All versions | 1.11.0-150000.3.3.1 | | `libnfs` | SUSE:Linux Enterprise Server for SAP applications 16.0 | All versions | 5.0.3-160000.4.1 | | `libnfs` | SUSE:Linux Micro 6.1 | All versions | 5.0.2-slfo.1.1_2.1 | | `libnfs` | openSUSE:Leap 16.0 | All versions | 5.0.3-160000.4.1 | ## How do I fix CVE-2026-53689? Apply the vendor's patch. ## Is CVE-2026-53689 being exploited? There is no known exploitation of CVE-2026-53689 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-53689 and fix it if it is affected. What it is: CVE-2026-53689 is a high-severity vulnerability in sahlberg libnfs, published on 10 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2026-53689 in the wild and no public exploit code. Affected product: sahlberg libnfs. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-53689/ (Markdown: https://insights.sbomify.com/CVE-2026-53689/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-53689 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-53689 - OSV: https://osv.dev/vulnerability/CVE-2026-53689 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-53689/ Summaries are generated and may contain mistakes; the official description above is the record.