{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-6688 exists.","fix":"No fix has been published for CVE-2026-6688 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-6688 is a high-severity memory corruption vulnerability in ChaN FatFs, published on 1 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-6688 and fix it if it is affected.\n\nWhat it is: CVE-2026-6688 is a high-severity memory corruption vulnerability in ChaN FatFs, published on 1 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-6688 exists.\n\nAffected product: ChaN FatFs. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-6688/ (Markdown: https://insights.sbomify.com/CVE-2026-6688/index.md)","id":"CVE-2026-6688","markdown":"https://insights.sbomify.com/CVE-2026-6688/index.md","name":"CVE-2026-6688","record":{"aliases":["GHSA-8vm2-mjff-2gg2"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"FatFs file system library","requires_auth":"none","summary":"Attackers can trigger buffer overflows in FatFs by providing long filenames, potentially leading to code execution or system crashes.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"runZero","cpe":[{"product":"fatfs","vendor":"elm-chan"}],"cvss":{"score":7.6,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-120","name":"Buffer Copy without Checking Size of Input"}],"description":"FatFs R0.16 and earlier contains a downstream-caller vulnerability pattern associated with FatFs long filename handling. With LFN enabled, fno.fname can be up to 255 characters; many callers copy it into short fixed buffers without bounds checks, causing overflow. This maps to CWE-120 (Buffer Copy without Checking Size of Input). Estimated CVSS v3.1 vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H (7.6, High). The estimated CISA SSVC vectors are Exploitation: PoC, Technical Impact: Total.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"FatFs Buffer Overflow via Unbounded LFN Filename Copy","id":"CVE-2026-6688","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"Mattermost doesn't enforce PermissionInviteUser when setting AllowOpenInvite or AllowedDomains during team creation","id":"CVE-2026-6689"},"packages":[],"prev":{"headline":"FatFs Stack Buffer Overflow via Uncapped exFAT Label Length","id":"CVE-2026-6687"},"products":["FatFs"],"published":"2026-07-01","related":[{"cvss_score":7.6,"headline":"FatFs Integer Overflow in FAT32 Volume Mount","id":"CVE-2026-6682","kev_date_added":null,"published":"2026-07-01"},{"cvss_score":7.6,"headline":"FatFs Stack Buffer Overflow via Uncapped exFAT Label Length","id":"CVE-2026-6687","kev_date_added":null,"published":"2026-07-01"},{"cvss_score":4.6,"headline":"FatFs Divide-by-Zero in exFAT Sync","id":"CVE-2026-6683","kev_date_added":null,"published":"2026-07-01"},{"cvss_score":4.6,"headline":"FatFs Infinite Loop in GPT Partition Scan","id":"CVE-2026-6684","kev_date_added":null,"published":"2026-07-01"},{"cvss_score":4.6,"headline":"FatFs Use of Uninitialized Clusters After Seek Past EOF","id":"CVE-2026-6686","kev_date_added":null,"published":"2026-07-01"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-07-01","vendors":["ChaN"]},"summary":"Attackers can trigger buffer overflows in FatFs by providing long filenames, potentially leading to code execution or system crashes.","url":"https://insights.sbomify.com/CVE-2026-6688/"}