CVE-2026-6688 json
FatFs Buffer Overflow via Unbounded LFN Filename Copy
published 2026-07-01 4 mo ago modified 2026-10-25 14 d ago also EUVD-2026-41000
- cvss
- 7.6
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 25%
- public exploits
- 0
- none known
Summary
FatFs R0.16 and earlier contains a downstream-caller vulnerability pattern associated with FatFs long filename handling. With LFN enabled, fno.fname can be up to 255 characters; many callers copy it into short fixed buffers without bounds checks, causing overflow. This maps to CWE-120 (Buffer Copy without Checking Size of Input). Estimated CVSS v3.1 vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H (7.6, High). The estimated CISA SSVC vectors are Exploitation: PoC, Technical Impact: Total.
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- total
- Assessed
- 4 mo ago
Exploit prediction
0.32% chance of exploitation in the next 30 days, higher than 25% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/runZeroInc/vulns-2026-fatfs-chance referenced PoC, tagged "exploit" by a source, unverified
- runzero.com https://www.runzero.com/blog/fatfs-bugs/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.6 | CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H |
Affected products
- ChaN FatFs
Classification
- Weakness
-
- CWE-120 Buffer Copy without Checking Size of Input
References
-
github.com
/runZeroInc/vulns-2026-fatfs-chance
technical-description, exploit, third-party-advisory
-
runzero.com
/blog/fatfs-bugs/
third-party-advisory, exploit
-
elm-chan.org
/fsw/ff/
product
-
runzero.com
/advisories/fatfs-long-fn-of-downstream-cve-2026-6688/
third-party-advisory
Sources
- CVE List CVE-2026-6688
- NVD CVE-2026-6688
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.