Skip to main content
Mallory
← Back to News
embedded-device-vulnerabilityopen-source-dependency-vulnerabilityproof-of-concept-releasewidely-deployed-product-advisory

Seven FatFs Flaws Expose Embedded Devices to Malicious Media and OTA Attacks

Vulnerability Disclosure · 9 sources · Updated 4mo ago · First seen Jul 1, 2026

Seven FatFs Flaws Expose Embedded Devices to Malicious Media and OTA Attacks

runZero disclosed seven vulnerabilities in the widely reused FatFs filesystem library, a FAT/exFAT implementation embedded in firmware for devices such as cameras, drones, industrial controllers, crypto wallets, and RTOS-based products. The flaws affect FAT, exFAT, and GPT parsing and can be triggered by crafted USB drives, SD cards, partition tables, or mounted firmware/update images, leading to memory corruption, denial of service, information disclosure, silent data corruption, and possible code execution. The most serious issues include CVE-2026-6682, an integer overflow in mount_volume() that can corrupt file-size metadata and enable downstream exploitation, and CVE-2026-6687, a stack overflow in f_getlabel() tied to exFAT label handling.

The disclosure warned that the blast radius is large because FatFs is vendored into ecosystems including ESP-IDF, STM32Cube, Zephyr, MicroPython, ArduPilot, RT-Thread, Mbed, TizenRT, and SWUpdate, with exploitation often requiring physical access but also potentially reaching devices through OTA workflows that automatically mount malicious images. runZero said all released versions are affected, only CVE-2026-6684 is fixed upstream in FatFs R0.16, and no coordinated maintainer response was received despite outreach through JPCERT/CC. Researchers published proof-of-concept disk images, a test harness, and a QEMU-based exploit example, while warning that downstream vendors will need to identify and patch their own bundled copies and that remediation may take years for many products.

Do you run this?See affected versions and whether adversaries are exploiting it.
Check your exposure
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

4 events · Jul 1, 2026 – Jul 3, 2026
  1. Jul 3, 20265mo ago

    FatFs R0.16 fixes CVE-2026-6684 upstream

    One of the seven disclosed issues, CVE-2026-6684, was already fixed upstream in FatFs R0.16. The references do not provide a specific release date for that upstream fix.

    Unpatched Flaws Disclosed in Filesystem Bundled Into Millions of Embedded Devices
  2. Jul 1, 20265mo ago

    runZero attempts maintainer contact and involves JPCERT/CC

    Before public disclosure, runZero said it tried to contact the FatFs maintainer and involved JPCERT/CC regarding the vulnerabilities. According to the references, the maintainer did not respond.

    Seven FatFs bugs, one very large blast radius
  3. Jul 1, 20265mo ago

    runZero releases FatFs PoCs and testing tools

    As part of the July 1 disclosure, runZero published proof-of-concept disk images, a test harness, and a QEMU-based exploit example to help demonstrate and assess the FatFs flaws. The company also said it released tooling to help downstream implementers identify and patch vendored copies.

    Seven FatFs bugs, one very large blast radius
  4. Jul 1, 20265mo ago

    runZero publicly discloses seven FatFs vulnerabilities

    On July 1, 2026, runZero disclosed seven vulnerabilities in the widely reused FatFs filesystem project affecting FAT, exFAT, and GPT parsing in embedded firmware ecosystems. The issues include memory corruption, denial of service, integer overflow, information disclosure, and logic flaws, with CVE-2026-6682 highlighted as the most severe.

    Seven FatFs bugs, one very large blast radius
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.