CVE-2026-64609 Apache Fory vulnerability
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.
Browse Information Disclosure security risksQuick answer
Apache Software Foundation Apache Fory should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- < 1.4.0
- < 0.11.0
Fixed versions
- Apply the latest vendor-supported patched version.
How to fix it
CVE-2026-64609 affects Apache Fory and involves memory-safety failure. A crafted input may corrupt memory, crash the process, or enable code execution in the affected context. Prioritize deployments that process untrusted input, expose the affected feature, or hold sensitive data. Upgrade Apache Fory to 1.4.0 and replace legacy org.apache.fury dependencies with the supported org.apache.fory coordinate where applicable.
- Inventory every deployment, device, package, plugin, container, build, and environment that uses Apache Fory.
- Compare the installed version with the recorded affected range: < 1.4.0, < 0.11.0.
- Upgrade Apache Fory to 1.4.0 and replace legacy org.apache.fury dependencies with the supported org.apache.fory coordinate where applicable.
- Until patched, limit untrusted files and peers, apply resource limits, and isolate the affected parser or service.
- Review configuration, roles, tokens, network paths, and exposed endpoints connected to Apache Fory; remove access that is not required.
- Review application, system, proxy, and audit logs for requests and behavior linked to the affected feature and CVE.
- If exploitation is suspected, isolate affected assets, preserve evidence, rotate exposed credentials or keys, restore trusted data, and rebuild compromised systems before returning them to service.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm every affected asset now runs the fixed vendor-supported release or has the documented mitigation for CVE-2026-64609 in place.
- Use a safe regression test to confirm the affected memory-safety failure path no longer produces the vulnerable behavior.
- Confirm temporary access controls, endpoint restrictions, network blocks, and least-privilege settings remain effective after the update.
- Review post-remediation logs and rerun Fixnx plus the relevant package, dependency, firmware, browser, or product-specific security check.
- Document affected assets, versions, changes, validation evidence, reviewed logs, and any credential rotation, cleanup, or replacement completed.
Related categories
Related security risks
More published guidance from the same primary category.
Trusted references
FAQ
What is affected by CVE-2026-64609?
Apache Software Foundation Apache Fory versions listed as affected should be reviewed: < 1.4.0, < 0.11.0.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.