Is CVE-2026-64609 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-64609 being exploited in the wild.

How severe is CVE-2026-64609?

Informational severity, with a CVSS score of 0, published 21 July 2026.

Which products and versions are affected?

Apache Software Foundation Fury 0.5.0 to 0.10.x; Apache Software Foundation Fury (fury-core) 0.5.0 to 0.10.x.

Is there a fix for CVE-2026-64609?

A patch was published on 2026-07-21: Fixed in version 1.4.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-64609 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-64609?

Check whether you run Apache Software Foundation Fury or Apache Software Foundation Fury (fury-core) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-64609: Apache Fory out-of-bounds read in zero-copy deserialization

CVE-2026-64609 · Severity: info · CVSS 0 · Published 2026-07-21

Apache Fory (formerly Fury) is a high-performance serialization framework used to convert data objects into formats suitable for storage or transmission. A security flaw exists in its optional 'zero-copy' feature that could allow an attacker to trigger an out-of-bounds memory read. While this specific report is categorized as low impact, memory safety issues in serialization libraries can sometimes lead to data exposure or application instability.

Technologies: Apache Software Foundation Fury. Vendors: Apache Software Foundation.

Quick answers

Is CVE-2026-64609 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-64609 being exploited in the wild.
How severe is CVE-2026-64609?: Informational severity, with a CVSS score of 0, published 21 July 2026.
Which products and versions are affected?: Apache Software Foundation Fury 0.5.0 to 0.10.x; Apache Software Foundation Fury (fury-core) 0.5.0 to 0.10.x.
Is there a fix for CVE-2026-64609?: A patch was published on 2026-07-21: Fixed in version 1.4.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-64609 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-64609?: Check whether you run Apache Software Foundation Fury or Apache Software Foundation Fury (fury-core) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

An out-of-bounds read vulnerability (CWE-125) exists in Apache Fory (formerly Apache Fury) within the `readAlignedVarUint()` function. The issue is triggered during out-of-band zero-copy deserialization when using `sun.misc.Unsafe` to read data, allowing the process to read beyond the boundaries of the underlying buffer. This is an opt-in feature; applications not explicitly using zero-copy deserialization are unaffected. An attacker could potentially exploit this to access sensitive memory or cause a Denial of Service (DoS). The vulnerability is addressed in version 1.4.0.

Affected products

Apache Software Foundation Apache Fory 0.5.0 to 1.3.x
Apache Software Foundation Apache Fury (fury-core) 0.5.0 to 0.10.x

Timeline

2026-07-21: advisory
2026-07-21: patched: Fixed in version 1.4.0

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.