CVE-2026-64609
Apache Fory out-of-bounds read
- Published21 Jul 2026
Description
Out-of-bounds read via sun.misc.Unsafe in Apache Fory. When out-of-band zero-copy deserialization is used, readAlignedVarUint() can read beyond the bounds of the underlying buffer. Out-of-band zero-copy deserialization is an opt-in feature; applications that do not use it are not affected. This issue affects Apache Fory (formerly Apache Fury): from 0.5.0 before 1.4.0. Versions before 0.11.0 were published under the Maven coordinates org.apache.fury:fury-core. Users are recommended to upgrade to version 1.4.0, which fixes the issue.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:HAffected products
Remediation
References
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-64609 being actively exploited?
CVE-2026-64609 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.78%.
How severe is CVE-2026-64609?
CVE-2026-64609 has a CVSS 3.1 base score of 9.1, rated critical. EPSS estimates a 0.78% probability of exploitation.
Which products are affected by CVE-2026-64609?
Affected products include Apache Fory.
How do I fix CVE-2026-64609?
Upgrade affected software to a fixed version, for example Apache Fory 1.4.0 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-64609 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.