CVE-2026-64608

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreHIGH confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-21. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.8; sources differ by 0.0.

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

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

Heap type confusion and out-of-bounds read/write in the Apache Fory C++ implementation. When deserializing data in compatible mode, the field-skip paths do not correctly validate the declared field types against the actual data, so input with an inconsistent schema can cause type confusion and out-of-bounds memory access. Only the C++ implementation is affected; other language implementations of Apache Fory are not.

This issue affects Apache Fory C++: from 0.14.0 before 1.4.0.

Users are recommended to upgrade to version 1.4.0, which fixes the issue.

CVSS v3
9.8
EG Score
9.8(high)
EG Risk
59(Track)
EG Risk 59/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
Severity98% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
29.7%
KEV
Not listed

Published

July 21, 2026

Last Modified

July 21, 2026

Advisory Details (2)

Auto-updated Jul 22, 2026
No patch confirmed yet.
generic

oss-security - CVE-2026-64608: Apache Fory: Heap type confusion and out-of-bounds read/write in C++ compatible-mode field-skip paths

http://www.openwall.com/lists/oss-security/2026/07/21/5
generic
https://lists.apache.org/thread/wl05slf57zzoq1s4pg4tk6nx6mjyjr4b

Vendor Advisories for CVE-2026-64608(1)

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

Weakness Classification(3)

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

Data Freshness Timeline

(refreshed 73× in last 7d / 73× 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-23 14:18 UTCEPSS rescore
  2. 2026-07-23 14:18 UTCEPSS rescore
  3. 2026-07-23 03:22 UTCEG score recompute
  4. 2026-07-22 23:19 UTCEG score recompute
  5. 2026-07-22 23:19 UTCGHSA enrichment
  6. 2026-07-22 14:08 UTCEPSS rescore
  7. 2026-07-22 14:08 UTCEPSS rescore
  8. 2026-07-21 13:58 UTCEG score recompute▲ 9.80
  9. 2026-07-21 13:57 UTCGHSA enrichment
  10. 2026-07-21 13:57 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
  11. 2026-07-21 13:56 UTCGHSA enrichment
  12. 2026-07-21 13:54 UTCGHSA enrichment
  13. 2026-07-21 13:53 UTCGHSA enrichment
  14. 2026-07-21 13:50 UTCGHSA enrichment
  15. 2026-07-21 13:50 UTCGHSA enrichment
  16. 2026-07-21 13:48 UTCGHSA enrichment
  17. 2026-07-21 13:48 UTCGHSA enrichment
  18. 2026-07-21 13:46 UTCGHSA enrichment
  19. 2026-07-21 13:46 UTCGHSA enrichment
  20. 2026-07-21 13:43 UTCGHSA enrichment
  21. 2026-07-21 13:40 UTCGHSA enrichment
  22. 2026-07-21 13:39 UTCGHSA enrichment
  23. 2026-07-21 13:37 UTCGHSA enrichment
  24. 2026-07-21 13:37 UTCGHSA enrichment
  25. 2026-07-21 13:35 UTCGHSA enrichment
Show 48 more
  1. 2026-07-21 13:35 UTCGHSA enrichment
  2. 2026-07-21 13:34 UTCGHSA enrichment
  3. 2026-07-21 13:33 UTCGHSA enrichment
  4. 2026-07-21 13:31 UTCGHSA enrichment
  5. 2026-07-21 13:27 UTCGHSA enrichment
  6. 2026-07-21 13:26 UTCGHSA enrichment
  7. 2026-07-21 13:25 UTCGHSA enrichment
  8. 2026-07-21 13:24 UTCGHSA enrichment
  9. 2026-07-21 13:23 UTCGHSA enrichment
  10. 2026-07-21 13:22 UTCGHSA enrichment
  11. 2026-07-21 13:20 UTCGHSA enrichment
  12. 2026-07-21 13:18 UTCGHSA enrichment
  13. 2026-07-21 13:18 UTCGHSA enrichment
  14. 2026-07-21 13:16 UTCGHSA enrichment
  15. 2026-07-21 13:14 UTCGHSA enrichment
  16. 2026-07-21 13:14 UTCGHSA enrichment
  17. 2026-07-21 13:13 UTCGHSA enrichment
  18. 2026-07-21 13:11 UTCGHSA enrichment
  19. 2026-07-21 13:10 UTCGHSA enrichment
  20. 2026-07-21 13:10 UTCGHSA enrichment
  21. 2026-07-21 13:09 UTCGHSA enrichment
  22. 2026-07-21 13:09 UTCGHSA enrichment
  23. 2026-07-21 13:06 UTCGHSA enrichment
  24. 2026-07-21 13:05 UTCGHSA enrichment
  25. 2026-07-21 13:05 UTCGHSA enrichment
  26. 2026-07-21 13:03 UTCGHSA enrichment
  27. 2026-07-21 13:03 UTCGHSA enrichment
  28. 2026-07-21 13:01 UTCGHSA enrichment
  29. 2026-07-21 13:00 UTCGHSA enrichment
  30. 2026-07-21 13:00 UTCGHSA enrichment
  31. 2026-07-21 12:58 UTCGHSA enrichment
  32. 2026-07-21 12:58 UTCGHSA enrichment
  33. 2026-07-21 12:47 UTCGHSA enrichment
  34. 2026-07-21 12:45 UTCGHSA enrichment
  35. 2026-07-21 12:44 UTCGHSA enrichment
  36. 2026-07-21 12:43 UTCGHSA enrichment
  37. 2026-07-21 12:41 UTCGHSA enrichment
  38. 2026-07-21 12:39 UTCGHSA enrichment
  39. 2026-07-21 12:39 UTCGHSA enrichment
  40. 2026-07-21 12:38 UTCGHSA enrichment
  41. 2026-07-21 12:36 UTCGHSA enrichment
  42. 2026-07-21 12:35 UTCGHSA enrichment
  43. 2026-07-21 12:35 UTCGHSA enrichment
  44. 2026-07-21 12:34 UTCGHSA enrichment
  45. 2026-07-21 12:33 UTCGHSA enrichment
  46. 2026-07-21 10:50 UTCNVD update
  47. 2026-07-21 10:09 UTCEG score recompute
  48. 2026-07-21 10:07 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-64608?
CVE-2026-64608 is a critical vulnerability published on July 21, 2026. Heap type confusion and out-of-bounds read/write in the Apache Fory C++ implementation. When deserializing data in compatible mode, the field-skip paths do not correctly validate the declared field types against the actual data, so input with an inconsistent schema can cause type confusion and…
When was CVE-2026-64608 disclosed?
CVE-2026-64608 was first published in the National Vulnerability Database on July 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64608 actively exploited?
CVE-2026-64608 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 29.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-64608?
CVE-2026-64608 has a CVSS v3.1 base score of 9.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-64608?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64608, 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-64608

Explore →

Is Your Infrastructure Affected by CVE-2026-64608?

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

Start Free Scan →Browse All CVEs