Loading vulnerability…
CVE-2026-6682 affects FatFs R0.16 and earlier. The vulnerability is an integer overflow in the FAT32 mount path, specifically in mount_volume(), where arithmetic involving the FAT size can wrap during calculation of filesystem metadata (described as fasize *= fs->n_fats). A crafted FAT32 filesystem image can cause the mount logic to derive incorrect internal size values, resulting in attacker-controlled file-size metadata. Downstream code may then trust those corrupted values as read lengths or related bounds, creating unsafe memory access conditions. Reported analysis indicates this can progress from malformed filesystem parsing to heap or stack memory corruption and possible code execution in real embedded deployments.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
11 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An integer overflow in FatFs FAT32 volume mounting that can lead to memory corruption and possible code execution when parsing malformed storage media or some firmware updates.
An integer overflow in FatFs mount_volume() for FAT32 that can produce attacker-controlled file-size metadata, potentially leading to heap/stack overflow and code execution.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.