CVE-2026-64609
Out-of-bounds read in Apache Fory zero-copy deserialization
Is CVE-2026-64609 being exploited?
Not confirmed. CVE-2026-64609 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.78% probability of exploitation in the next 30 days.
How severe is CVE-2026-64609?
CVE-2026-64609 is rated Critical with a CVSS score of 9.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-64609?
Yes. A fix has been recorded for CVE-2026-64609. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-64609 affect?
CVE-2026-64609 affects Apache Fory 0.5.0 to <1.4.0, org.apache.fury:fury-core versions <0.11.0. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-64609?
Upgrade to Apache Fory 1.4.0; disable out-of-band zero-copy deserialization if unused.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Crafted serialized input can trigger out-of-bounds read via sun.misc.Unsafe, enabling memory disclosure or crash (DoS) when opt-in zero-copy deserialization is enabled.
Patch when possible
- affected>= 0.11.0 and < 1.4.0
- affected>= 0.5.0 and < 0.11.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.