Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2026-6682: FAT32 Integer Overflow in FatFs mount_volume()

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-6682CWE-190 · Integer Overflow or Wraparound

CVE-2026-6682 affects FatFs R0.16 and earlier. During FAT32 volume mounting in mount_volume(), an integer multiplication used in FAT size calculation (described as fasize *= fs->n_fats) can overflow and wrap. A crafted FAT32 filesystem image can therefore cause incorrect internal filesystem metadata, including attacker-controlled file-size values. Downstream code may later trust those corrupted size values as legitimate read lengths, creating unsafe memory operations. In real deployments this can lead to heap or stack corruption, and the published research describes possible code execution as a consequence.

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 cause memory corruption during subsequent filesystem operations after a malicious FAT32 volume is mounted. The reported outcomes include heap overflow or stack overflow, process or device instability, crashes, and potential arbitrary code execution. Because FatFs is widely embedded in devices that often lack modern memory protections, the practical impact can extend to full compromise of affected embedded systems. The source material also notes possible exposure through OTA/update pipelines, which broadens impact beyond removable media.

Mitigation

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

Do not process untrusted FAT32 media or filesystem images on affected devices until a fix is deployed. Restrict or disable exposure to removable media interfaces such as USB and SD where feasible, and harden OTA/update workflows so untrusted or unsigned filesystem images cannot reach FatFs parsing paths. Additional defensive measures include validating filesystem images before mounting, isolating parsing components where possible, and reviewing downstream callers that use mounted filesystem metadata as read lengths.

Remediation

Patch, then assume compromise.

Upgrade to a vendor-supplied fixed version of FatFs or apply a downstream patch that prevents integer wraparound in FAT32 mount arithmetic within mount_volume(). Specifically, FAT size calculations should be bounds-checked before multiplication and validated for overflow before derived metadata is trusted. Because the content indicates no broadly available upstream fix for this issue at disclosure time, downstream integrators should audit vendored FatFs copies and backport a fix, then validate all code paths that consume file-size metadata derived during mount.

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-6682 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-6682 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-6682?
Yes. As of Sep 25, 2026, Mallory has reports of a public exploit for CVE-2026-6682.
Is there a patch for CVE-2026-6682?
Upgrade to a vendor-supplied fixed version of FatFs or apply a downstream patch that prevents integer wraparound in FAT32 mount arithmetic within mount_volume(). Specifically, FAT size calculations should be bounds-checked before multiplication and validated for overflow before derived metadata is trusted.
What products are affected by CVE-2026-6682?
Elm-Chan Fatfs.
How severe is CVE-2026-6682?
CVE-2026-6682 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

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

View more in app →
+3 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 activity15Community discussion across Reddit, Mastodon, and other social sources.