CVE-2026-6687

HIGHPre-NVD 7.67.6—
EchelonGraph scoreHIGH confidence

Score 7.6 from GitHub Security Advisory (severity: HIGH) published 2026-07-01. a secondary CVSS source baseline 7.6; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.6
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.6Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

FatFs R0.16 and earlier contains a stack overflow bug in f_getlabel() because exFAT label length (XDIR_NumLabel) is trusted without enforcing spec maximums. This maps to CWE-121 (Stack-based Buffer Overflow). 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.

CVSS v3
7.6
EG Score
7.6(high)
EPSS
14.1%
KEV
Not listed

Published

July 1, 2026

Last Modified

July 2, 2026

Advisory Details (3)

Auto-updated Jul 2, 2026
⚠️ Active exploitation confirmed. No patch confirmed yet.
generic

GitHub - runZeroInc/vulns-2026-fatfs-chance · GitHub

https://github.com/runZeroInc/vulns-2026-fatfs-chance
generic🔴 Active Exploitation

Seven FatFs bugs, one very large blast radius

https://www.runzero.com/blog/fatfs-bugs/
generic🔴 Active Exploitation

FatFS exFAT label-length stack overflow in f_getlabel()

https://www.runzero.com/advisories/fatfs-exfat-label-len-of-cve-2026-6687/

Vendor Advisories for CVE-2026-6687(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 32× in last 7d / 32× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-07 05:06 UTCEG score recompute
  2. 2026-07-07 05:05 UTCGHSA enrichment
  3. 2026-07-06 17:00 UTCEG score recompute
  4. 2026-07-06 16:59 UTCGHSA enrichment
  5. 2026-07-06 16:27 UTCEPSS rescore
  6. 2026-07-06 16:27 UTCEPSS rescore
  7. 2026-07-06 04:55 UTCEG score recompute
  8. 2026-07-06 04:55 UTCGHSA enrichment
  9. 2026-07-06 02:23 UTCEPSS rescore
  10. 2026-07-06 02:23 UTCEPSS rescore
  11. 2026-07-05 16:51 UTCEG score recompute
  12. 2026-07-05 16:50 UTCGHSA enrichment
  13. 2026-07-05 04:45 UTCEG score recompute
  14. 2026-07-05 04:45 UTCGHSA enrichment
  15. 2026-07-05 02:31 UTCEPSS rescore
  16. 2026-07-05 02:30 UTCEPSS rescore
  17. 2026-07-04 16:36 UTCEG score recompute
  18. 2026-07-04 16:36 UTCGHSA enrichment
  19. 2026-07-04 06:31 UTCEPSS rescore
  20. 2026-07-04 06:31 UTCEPSS rescore
  21. 2026-07-04 04:29 UTCEG score recompute
  22. 2026-07-04 04:29 UTCGHSA enrichment
  23. 2026-07-03 16:22 UTCEG score recompute
  24. 2026-07-03 16:22 UTCGHSA enrichment
  25. 2026-07-03 04:18 UTCEG score recompute
Show 7 more
  1. 2026-07-03 04:18 UTCGHSA enrichment
  2. 2026-07-02 16:10 UTCEG score recompute
  3. 2026-07-02 16:10 UTCGHSA enrichment
  4. 2026-07-02 04:06 UTCEG score recompute
  5. 2026-07-02 04:06 UTCGHSA enrichment
  6. 2026-07-01 16:02 UTCEG score recompute
  7. 2026-07-01 16:02 UTCGHSA enrichment

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-6687?
CVE-2026-6687 is a high vulnerability published on July 1, 2026. FatFs R0.16 and earlier contains a stack overflow bug in fgetlabel() because exFAT label length (XDIRNumLabel) is trusted without enforcing spec maximums. This maps to CWE-121 (Stack-based Buffer Overflow). 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…
When was CVE-2026-6687 disclosed?
CVE-2026-6687 was first published in the National Vulnerability Database on July 1, 2026, with the most recent update on July 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-6687 actively exploited?
CVE-2026-6687 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 14.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-6687?
CVE-2026-6687 has a CVSS v3 base score of 7.6 (NVD).
How do I remediate CVE-2026-6687?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-6687, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-6687

Explore →

Is Your Infrastructure Affected by CVE-2026-6687?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs