dbcve.org
ForyApplication · Apache

CVE-2026-64609

CRITICAL · 9.1 CVSS v3.1 Published 2026-07-21
Fix available
A fix is available. Upgrade to 1.4.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 4 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Apache Fory (formerly Apache Fury) contains an out-of-bounds read vulnerability in the readAlignedVarUint() function when using the opt-in out-of-band zero-copy deserialization feature. The vulnerability stems from improper bounds checking in sun.misc.Unsafe usage, allowing reads beyond the buffer boundary. This is a critical memory safety issue with CVSS 9.1.

MitigationUpgrade Apache Fory to version 1.4.0 or later. Alternatively, if immediate upgrade is not feasible, disable the out-of-band zero-copy deserialization feature as a temporary mitigation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ForyApplication
Affected:>= 0.5.0, < 1.4.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Apache Fory installation and version
    Search for Apache Fory libraries in your project dependencies (Maven pom.xml, Gradle build files, or JAR files in classpath). Look for artifact 'org.apache.fory:fory-core' or similar. Note the exact version number.
    Affected if The installed version is 0.5.0 or higher but lower than 1.4.0
  2. Check for zero-copy deserialization feature usage
    Search your codebase for references to zero-copy deserialization APIs. Look for classes like 'ForySerializer' with zero-copy options, or configuration properties involving 'zeroCopy', 'outOfBand', or 'offHeap' deserialization. Review any custom serializer implementations that may enable this feature.
    Affected if Zero-copy deserialization is explicitly enabled or used in the application code or configuration
  3. Inspect serialization configuration
    Review serialization configuration files or code that initializes Fury/Fory serializers. Look for builder patterns or configuration objects that set enableZeroCopy(), useOffHeapBuffers(), or similar methods.
    Affected if The configuration explicitly enables zero-copy or out-of-band deserialization options
  4. Verify runtime dependency versions
    At runtime, inspect the actual JAR files loaded in the application. Check the manifest or version info of the fury-core or fory-core library on the classpath to confirm the exact version being used.
    Affected if The runtime version resolves to >=0.5.0 and <1.4.0

You are affected if your environment has Apache Fory version 0.5.0 through less than 1.4.0 AND has zero-copy deserialization feature enabled or in use.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.4.0 or later
Fixed in 1.4.0
Interim mitigation

Upgrade Apache Fory to version 1.4.0 or later. Alternatively, if immediate upgrade is not feasible, disable the out-of-band zero-copy deserialization feature as a temporary mitigation.

Recommended fix High confidence

1.4.0

  1. Locate the Maven pom.xml or Gradle build.gradle file in your project that declares the Apache Fory or Fury dependency
  2. Update the dependency version to 1.4.0 (e.g., change org.apache.fury:fury-core or org.apache.fory:fory-core to version 1.4.0)
  3. Run mvn clean compile or gradle build to rebuild the project with the updated dependency
  4. Redeploy the updated application

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Fory Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,020
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,232.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-64609 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-64609 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data