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.
CVE-2026-53689
Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-06-10. a secondary CVSS source baseline 7.1; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 7.1
- EG Score
- 7.1(medium)
- EG Risk
- 32(Track)EG Risk 32/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity71% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 11%
- KEV
- Not listed
Published
June 10, 2026
Last Modified
July 19, 2026
Advisory Details (1)
Auto-updated Jun 11, 2026commit 55c18ea33a83 (sahlberg/libnfs)
Fix landed in sahlberg/libnfs commit 55c18ea33a83 — awaiting tagged release
https://github.com/sahlberg/libnfs/commit/55c18ea33a83d667f79f0ef209c96895795c729fVendor Advisories for CVE-2026-53689(2)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(1)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| ubuntu | libnfs14 (5.0.2-1ubuntu1.1) @ resolute | 2026-08-25 | ubuntu |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(4 across 4 ecosystems)
Debian:11(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| libnfs | 4.0.0-1 | 4.0.0-1+deb11u1 | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| libnfs | 4.0.0-1 | 4.0.0-1+deb12u1 | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| libnfs | 5.0.2-1, 5.0.2-1+deb13u1, 5.0.2-1.1 | — | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| libnfs | 5.0.2-1 | 5.0.2-1.1 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Additional Vendor Advisories
(1)
Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.
Data Freshness Timeline
(refreshed 26× in last 7d / 141× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 317 total refreshes for this CVE.
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-25 00:24 UTCEG score recompute
- 2026-08-25 00:24 UTCVendor advisory
- 2026-08-25 00:24 UTCGHSA enrichment
- 2026-08-23 23:26 UTCVendor advisory
- 2026-08-23 23:26 UTCGHSA enrichment
- 2026-08-23 10:48 UTCEG score recompute
- 2026-08-23 10:48 UTCVendor advisory
- 2026-08-23 10:48 UTCGHSA enrichment
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 22:44 UTCVendor advisory
- 2026-08-21 22:44 UTCGHSA enrichment
- 2026-08-21 09:58 UTCEG score recompute
- 2026-08-21 09:58 UTCVendor advisory
- 2026-08-21 09:58 UTCGHSA enrichment
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 21:25 UTCVendor advisory
- 2026-08-20 21:25 UTCGHSA enrichment
- 2026-08-20 08:53 UTCEG score recompute
- 2026-08-20 08:53 UTCVendor advisory
- 2026-08-20 08:53 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 14:57 UTCEG score recompute
- 2026-08-19 14:57 UTCVendor advisory
Show 75 moreShow fewer
- 2026-08-19 14:57 UTCGHSA enrichment
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 14:07 UTCEG score recompute
- 2026-08-17 14:07 UTCVendor advisory
- 2026-08-17 14:07 UTCGHSA enrichment
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 01:35 UTCEG score recompute
- 2026-08-17 01:35 UTCVendor advisory
- 2026-08-17 01:35 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 12:58 UTCEG score recompute
- 2026-08-16 12:58 UTCVendor advisory
- 2026-08-16 12:58 UTCGHSA enrichment
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-16 00:26 UTCVendor advisory
- 2026-08-16 00:26 UTCGHSA enrichment
- 2026-08-15 11:53 UTCEG score recompute
- 2026-08-15 11:53 UTCVendor advisory
- 2026-08-15 11:53 UTCGHSA enrichment
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 23:20 UTCVendor advisory
- 2026-08-14 23:20 UTCGHSA enrichment
- 2026-08-14 10:48 UTCVendor advisory
- 2026-08-14 10:48 UTCGHSA enrichment
- 2026-08-13 22:16 UTCEG score recompute
- 2026-08-13 22:16 UTCVendor advisory
- 2026-08-13 22:16 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 03:31 UTCVendor advisory
- 2026-08-13 03:31 UTCGHSA enrichment
- 2026-08-12 14:59 UTCEG score recompute
- 2026-08-12 14:59 UTCVendor advisory
- 2026-08-12 14:59 UTCGHSA enrichment
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-12 02:27 UTCVendor advisory
- 2026-08-12 02:27 UTCGHSA enrichment
- 2026-08-11 13:55 UTCEG score recompute
- 2026-08-11 13:55 UTCVendor advisory
- 2026-08-11 13:55 UTCGHSA enrichment
- 2026-08-11 01:23 UTCEG score recompute
- 2026-08-11 01:23 UTCVendor advisory
- 2026-08-11 01:23 UTCGHSA enrichment
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 12:51 UTCVendor advisory
- 2026-08-10 12:51 UTCGHSA enrichment
- 2026-08-10 00:19 UTCEG score recompute
- 2026-08-10 00:19 UTCVendor advisory
- 2026-08-10 00:19 UTCGHSA enrichment
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 11:47 UTCVendor advisory
- 2026-08-09 11:47 UTCGHSA enrichment
- 2026-08-08 23:15 UTCEG score recompute
- 2026-08-08 23:15 UTCVendor advisory
- 2026-08-08 23:15 UTCGHSA enrichment
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 10:42 UTCVendor advisory
- 2026-08-08 10:41 UTCGHSA enrichment
- 2026-08-07 22:09 UTCEG score recompute
- 2026-08-07 22:09 UTCVendor advisory
- 2026-08-07 22:09 UTCGHSA enrichment
- 2026-08-07 09:37 UTCVendor advisory
- 2026-08-07 09:37 UTCGHSA enrichment
- 2026-08-06 21:05 UTCEG score recompute
- 2026-08-06 21:05 UTCVendor advisory
- 2026-08-06 21:05 UTCGHSA enrichment
- 2026-08-06 13:47 UTCEPSS rescore
- 2026-08-06 08:33 UTCVendor advisory
- 2026-08-06 08:33 UTCGHSA enrichment
- 2026-08-05 20:01 UTCEG score recompute
- 2026-08-05 20:01 UTCVendor advisory
- 2026-08-05 20:01 UTCGHSA enrichment
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-04 15:56 UTCEG score recompute
- 2026-08-04 15:56 UTCVendor advisory
- 2026-08-04 15:56 UTCGHSA enrichment
Frequently asked(5)
What is CVE-2026-53689?
When was CVE-2026-53689 disclosed?
Is CVE-2026-53689 actively exploited?
What is the CVSS score of CVE-2026-53689?
How do I remediate CVE-2026-53689?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-53689
Is Your Infrastructure Affected by CVE-2026-53689?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.