CVE-2026-10709

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

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

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

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

A maliciously crafted FBX file, when parsed through Autodesk FBX SDK, can trigger a stack-based buffer overflow vulnerability in fbxsdk::FbxIO::BinaryReadSectionHeader. A malicious actor can leverage this vulnerability to execute arbitrary code in the context of the current process.

CVSS v3
7.8
EG Score
7.8(high)
EG Risk
35(Track)
EG Risk 35/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
4%
KEV
Not listed

Published

August 4, 2026

Last Modified

August 5, 2026

References (2)

Vendor Advisories for CVE-2026-10709(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 26× in last 7d / 71× 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-08-21 04:57 UTCEG score recompute
  2. 2026-08-21 04:57 UTCGHSA enrichment
  3. 2026-08-20 22:55 UTCEPSS rescore
  4. 2026-08-20 16:12 UTCGHSA enrichment
  5. 2026-08-20 03:25 UTCEG score recompute
  6. 2026-08-20 03:25 UTCGHSA enrichment
  7. 2026-08-19 17:03 UTCEPSS rescore
  8. 2026-08-19 14:39 UTCGHSA enrichment
  9. 2026-08-19 01:34 UTCEG score recompute
  10. 2026-08-19 01:34 UTCGHSA enrichment
  11. 2026-08-18 13:48 UTCEPSS rescore
  12. 2026-08-18 12:49 UTCGHSA enrichment
  13. 2026-08-17 23:19 UTCEG score recompute
  14. 2026-08-17 23:19 UTCGHSA enrichment
  15. 2026-08-17 10:34 UTCGHSA enrichment
  16. 2026-08-16 21:49 UTCEG score recompute
  17. 2026-08-16 21:49 UTCGHSA enrichment
  18. 2026-08-16 14:56 UTCEPSS rescore
  19. 2026-08-16 09:04 UTCEG score recompute
  20. 2026-08-16 09:04 UTCGHSA enrichment
  21. 2026-08-16 02:14 UTCEPSS rescore
  22. 2026-08-15 20:20 UTCGHSA enrichment
  23. 2026-08-15 07:35 UTCEG score recompute
  24. 2026-08-15 07:35 UTCGHSA enrichment
  25. 2026-08-15 01:30 UTCEPSS rescore
Show 46 more
  1. 2026-08-14 18:50 UTCGHSA enrichment
  2. 2026-08-14 06:06 UTCEG score recompute
  3. 2026-08-14 06:06 UTCGHSA enrichment
  4. 2026-08-13 22:00 UTCEPSS rescore
  5. 2026-08-13 17:21 UTCGHSA enrichment
  6. 2026-08-13 04:37 UTCGHSA enrichment
  7. 2026-08-12 15:52 UTCEG score recompute
  8. 2026-08-12 15:52 UTCGHSA enrichment
  9. 2026-08-12 13:50 UTCEPSS rescore
  10. 2026-08-12 03:08 UTCGHSA enrichment
  11. 2026-08-11 14:23 UTCEG score recompute
  12. 2026-08-11 14:23 UTCGHSA enrichment
  13. 2026-08-11 13:42 UTCEPSS rescore
  14. 2026-08-11 01:38 UTCEG score recompute
  15. 2026-08-11 01:38 UTCGHSA enrichment
  16. 2026-08-10 23:59 UTCEPSS rescore
  17. 2026-08-10 12:53 UTCGHSA enrichment
  18. 2026-08-10 00:08 UTCEG score recompute
  19. 2026-08-10 00:08 UTCGHSA enrichment
  20. 2026-08-09 13:46 UTCEPSS rescore
  21. 2026-08-09 11:24 UTCGHSA enrichment
  22. 2026-08-08 22:39 UTCEG score recompute
  23. 2026-08-08 22:39 UTCGHSA enrichment
  24. 2026-08-08 16:37 UTCEPSS rescore
  25. 2026-08-08 09:54 UTCGHSA enrichment
  26. 2026-08-07 21:10 UTCEG score recompute
  27. 2026-08-07 21:10 UTCGHSA enrichment
  28. 2026-08-07 08:25 UTCGHSA enrichment
  29. 2026-08-06 19:40 UTCEG score recompute
  30. 2026-08-06 19:40 UTCGHSA enrichment
  31. 2026-08-06 13:46 UTCEPSS rescore
  32. 2026-08-06 06:55 UTCEG score recompute
  33. 2026-08-06 06:55 UTCGHSA enrichment
  34. 2026-08-05 19:17 UTCEPSS rescore
  35. 2026-08-05 18:10 UTCGHSA enrichment
  36. 2026-08-05 05:26 UTCEG score recompute
  37. 2026-08-05 05:25 UTCGHSA enrichment
  38. 2026-08-05 04:36 UTCEG score recompute
  39. 2026-08-05 04:36 UTCGHSA enrichment
  40. 2026-08-04 17:24 UTCEG score recompute
  41. 2026-08-04 17:24 UTCGHSA enrichment
  42. 2026-08-04 16:29 UTCEG score recompute
  43. 2026-08-04 16:29 UTCGHSA enrichment
  44. 2026-08-04 13:26 UTCEG score recompute
  45. 2026-08-04 13:13 UTCEG score recompute
  46. 2026-08-04 13:13 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-10709?
CVE-2026-10709 is a high vulnerability published on August 4, 2026. A maliciously crafted FBX file, when parsed through Autodesk FBX SDK, can trigger a stack-based buffer overflow vulnerability in fbxsdk::FbxIO::BinaryReadSectionHeader. A malicious actor can leverage this vulnerability to execute arbitrary code in the context of the current process.
When was CVE-2026-10709 disclosed?
CVE-2026-10709 was first published in the National Vulnerability Database on August 4, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-10709 actively exploited?
CVE-2026-10709 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 95.7% of all scored CVEs.
What is the CVSS score of CVE-2026-10709?
CVE-2026-10709 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-10709?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-10709, 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-10709

Explore →

Is Your Infrastructure Affected by CVE-2026-10709?

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

Start Free Scan →Browse All CVEs