Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2026-6688: FatFs long filename overflow in downstream callers

Published Jul 1, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.6High · v3.1
EPSS0.32%26th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Elm-Chan
IdentifiersCVE-2026-6688CWE-120 · Buffer Copy without Checking Size…

CVE-2026-6688 affects FatFs R0.16 and earlier and is associated with long filename (LFN) handling in downstream integrations. When LFN support is enabled, the filename returned in fno.fname can be as long as 255 characters. Many downstream wrappers and application callers incorrectly copy fno.fname into smaller fixed-size buffers using unsafe operations such as strcpy or sprintf without validating the destination size. This creates a downstream-caller buffer overflow condition. The issue is not described as a single vulnerable FatFs function performing the overflow itself; rather, FatFs exposes long filename data that downstream code frequently mishandles, making this a recurring integration bug pattern across embedded firmware ecosystems that vendor FatFs.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can overflow fixed-size buffers in wrapper or application code that handles FatFs filenames, leading to memory corruption. In embedded targets, this may result in crashes, denial of service, corruption of adjacent stack or heap data, and potentially arbitrary code execution depending on compiler layout, memory protections, and the affected caller logic. Because many embedded deployments lack mitigations such as ASLR or stronger memory protections, the practical impact can extend to full compromise of confidentiality, integrity, and availability.

Mitigation

If you can’t patch tonight, do this now.

If immediate code fixes are not possible, disable long filename (LFN) support where operationally feasible, restrict acceptance of untrusted removable media and filesystem images, and harden any update or mount workflow that processes attacker-controlled FAT/exFAT content. Add defensive validation before copying or formatting filenames, reject overlong names at integration boundaries, and reduce exposure by limiting physical access to USB ports, SD slots, and other media ingestion paths.

Remediation

Patch, then assume compromise.

Audit all downstream code paths that consume FatFs filename output, especially uses of fno.fname in wrappers, path-building helpers, logging code, UI code, and file-management routines. Replace unsafe copies and formatting operations such as strcpy and sprintf with bounded alternatives, enforce explicit destination-length checks, and size buffers for worst-case LFN input or safely truncate with clear error handling. Where available, upgrade beyond FatFs R0.16 if a fixed release addressing related handling exists, but the provided material indicates that fully fixing this issue requires downstream wrapper-level changes rather than a library-only update.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Elm-ChanFatfsapplication
FAQ

Frequently asked questions

Is CVE-2026-6688 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-6688 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-6688?
Yes. As of Sep 25, 2026, Mallory has reports of a public exploit for CVE-2026-6688.
Is there a patch for CVE-2026-6688?
Audit all downstream code paths that consume FatFs filename output, especially uses of fno.fname in wrappers, path-building helpers, logging code, UI code, and file-management routines. Replace unsafe copies and formatting operations such as strcpy and sprintf with bounded alternatives, enforce explicit destination-length checks, and size buffers for worst-case LFN input or safely truncate with clear error handling.
What products are affected by CVE-2026-6688?
Elm-Chan Fatfs.
How severe is CVE-2026-6688?
CVE-2026-6688 has a CVSS v3.1 score of 7.6 (High) and an EPSS score of 0.32% (26th percentile) as of Sep 25, 2026.
Activity feed

Recent activity

14 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+2 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity8Community discussion across Reddit, Mastodon, and other social sources.