External risk intelligence

Apache Fory Out-of-Bounds Read Vulnerability in Zero-Copy Deserialization

CVE advisorySeverity: CRITICAL (CVSS 9.1)

CVE-2026-64609

Apache Fory is a serialization framework library integrated into application codebases. While it can be used in internet-facing services to process data, the vulnerability requires the use of an opt-in zero-copy deserialization feature. Its deployment is embedded within applications rather than being a standalone internet-facing service or appliance.

Out-of-bounds Read

Halo Surface Signal: 3 out of 5 — possibly public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This vulnerability involves the Apache Fory serialization library, specifically when an optional feature called "out-of-band zero-copy deserialization" is enabled. If this feature is used, a flaw allows reading beyond the intended data boundaries, which could potentially lead to information disclosure or denial of service. Applications not using this specific opt-in feature are unaffected.

  • A library flaw impacts data handling if a specific feature is active.
  • It matters if your applications use a specialized deserialization method.
  • Confirm if the specialized feature is in use before taking action.

Attack Path

How an attacker could exploit the issue

An attacker could target applications that have explicitly enabled Apache Fory's out-of-band zero-copy deserialization feature. By sending specially crafted data to these applications, an attacker could trigger a flaw in the `readAlignedVarUint()` function, causing it to read beyond the expected data boundaries. This could potentially allow an attacker to access sensitive information or disrupt application operation.

  • Requires opt-in feature enabled.
  • Triggers read beyond buffer bounds.
  • Can lead to data access or crashes.

Live Threat

Current exploitation, exposure, and threat context

When the opt-in out-of-band zero-copy deserialization feature is enabled in Apache Fory, an out-of-bounds read vulnerability could allow an attacker to read beyond the allocated buffer. This could potentially impact the integrity of the deserialization process and lead to service instability.

  • System memory data at risk.
  • Via crafted serialized input data.
  • Could cause denial of service.

Operational Fix

Recommended remediation, mitigation, and detection steps

Application owners and platform teams are likely responsible for addressing this critical vulnerability in Apache Fory, particularly if the opt-in out-of-band zero-copy deserialization feature is in use. The first practical step is to identify all instances of Apache Fory within your environment, confirm if the affected feature is enabled and if the instances are exposed or critical, and then ascertain the accountable owner for remediation.

  • Application owners and platform teams.
  • Verify Fory usage and feature enablement.
  • Plan remediation or risk reduction.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Apache Fory?

Apache Fory (formerly known as Apache Fury) is a high-performance serialization framework used by developers to convert complex data structures into a format suitable for storage or network transmission. It is typically integrated as a library directly into Java application codebases to accelerate data processing. Because it is a library rather than a standalone server, it functions as a component within the larger applications that choose to include it.

What does CWE-125 mean for CVE-2026-64609?

CWE-125 refers to an out-of-bounds read vulnerability. In the context of CVE-2026-64609, this means the software attempts to read data past the end of an allocated memory buffer. When this happens, the application may inadvertently access or return memory that it is not supposed to read, potentially leading to unauthorized information disclosure or triggering an application crash, which results in a denial of service.

How is this vulnerability triggered?

The flaw is triggered when an application processes specially crafted input data while using the library's opt-in 'out-of-band zero-copy deserialization' feature. The error occurs within the `readAlignedVarUint()` function. Crucially, if your application uses Apache Fory but has not explicitly enabled this specific zero-copy deserialization method, it is not susceptible to this vulnerability.

Why should I care about this vulnerability?

You should care if your applications process untrusted network input using the affected zero-copy feature. According to Halo Surface Signal, because Apache Fory is embedded within your software, the risk depends on how your specific application utilizes it. If your service is internet-facing and uses this deserialization mode, an attacker could potentially reach the vulnerable code path through crafted data requests.

What is the first step to address CVE-2026-64609?

Your first step is to perform an inventory of your application stack to identify where Apache Fory is included. Once identified, consult your development team to determine if the 'out-of-band zero-copy deserialization' feature is actively enabled in your configuration. If you confirm the feature is in use, plan to update to version 1.4.0, which contains the necessary fix for this memory safety issue.

References