CVE-2026-6687: exFAT label-length stack overflow in FatFs f_getlabel()
- Vendor
- Elm-Chan
FatFs R0.16 and earlier contains a stack-based buffer overflow in the exFAT handling path of f_getlabel(). The vulnerability exists because the function trusts the exFAT volume-label length field (XDIR_NumLabel) and does not enforce the specification maximum before copying the label into a caller-provided buffer. A crafted exFAT filesystem can therefore supply an oversized label length that causes f_getlabel() to perform an oversized write into a stack-resident label buffer, resulting in memory corruption in embedded firmware that uses the library.
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 corrupt stack memory and compromise confidentiality, integrity, and availability. In affected embedded deployments, this may cause crashes, denial of service, or potentially arbitrary code execution, especially where common exploit mitigations such as ASLR or strong memory protections are absent. The provided advisory estimates CVSS v3.1 7.6 (High) with vector AV:P/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H.
Mitigation
If you can’t patch tonight, do this now.
Until a fixed release is available, reduce exposure by preventing untrusted exFAT media from being mounted or inspected, especially via USB and SD interfaces. Disable exFAT support where not required, restrict physical access to removable-media ports, and avoid automatically processing externally supplied storage images. Downstream integrators can also add defensive bounds checks around label handling and harden callers so destination buffers are size-checked before use.
Remediation
Patch, then assume compromise.
Upgrade to a fixed FatFs release newer than R0.16 once one is made available by the maintainer or vendor. Because FatFs is commonly vendored into downstream SDKs and firmware stacks, downstream maintainers should patch their bundled copies, audit all uses of f_getlabel(), and ensure exFAT label lengths are validated and capped to the specification maximum before copying into destination buffers.
Exploits
No public exploits tracked yet. Mallory keeps watching.
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.
References
Frequently asked questions
- Is CVE-2026-6687 exploited in the wild?
- As of Sep 25, 2026, Mallory has no reports of CVE-2026-6687 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-6687?
- Yes. As of Sep 25, 2026, Mallory has reports of a public exploit for CVE-2026-6687.
- Is there a patch for CVE-2026-6687?
- Upgrade to a fixed FatFs release newer than R0.16 once one is made available by the maintainer or vendor. Because FatFs is commonly vendored into downstream SDKs and firmware stacks, downstream maintainers should patch their bundled copies, audit all uses of f_getlabel(), and ensure exFAT label lengths are validated and capped to the specification maximum before copying into destination buffers.
- What products are affected by CVE-2026-6687?
- Elm-Chan Fatfs.
- How severe is CVE-2026-6687?
- CVE-2026-6687 has a CVSS v3.1 score of 7.6 (High) and an EPSS score of 0.35% (29th percentile) as of Sep 25, 2026.
Recent activity
15 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.