- Product: Apache Software Foundation Apache Fory
- Vulnerabilities: 4 flaws (CVE-2026-64606, CVE-2026-64608, CVE-2026-60080, CVE-2026-64609)
- Highest severity: 9.8 (Critical · CVSSv3)
- Worst impact: Class-registration bypass through an auto-admitted SerializedLambda capturing interface
- Status: No confirmed exploitation yet; patches available
- Action: Update to 1.4.0, 0.11.0 now
| CVE | CVSS (CVSSv3) | Type | Fixed in | Status |
|---|---|---|---|---|
| CVE-2026-64606 | 9.8 | CWE-502 | 1.4.0, 0.11.0 | Not exploited |
| CVE-2026-64608 | 9.8 | CWE-502 | 1.4.0 | Not exploited |
| CVE-2026-64609 | 9.1 | CWE-125 | 1.4.0, 0.11.0 | Not exploited |
| CVE-2026-60080 | 7.3 | CWE-416 | — | Not exploited |
TL;DR
The Apache Fory project disclosed four vulnerabilities on July 21, 2026. Three carry an important rating, and one is moderate. Version 1.4.0 fixes all of them.
Why it matters
Fory is a fast serialization framework for cross-language data exchange. Serialization code sits directly in the path of untrusted input. So bugs here can turn a data feed into an attack surface. These Apache Fory vulnerabilities span three language implementations at once. That breadth is unusual and widens the blast radius. Notably, the project has patched several deserialization issues this year already.
How the attacks work
Java: class-registration bypass
CVE-2026-64606 is the one to watch. It lets attackers bypass class-registration checks during Java lambda deserialization. Registration allowlists are a core defense against deserialization attacks. Only the lambda capture class is affected.
C++: type confusion
CVE-2026-64608 hits the C++ implementation only. In compatible mode, field-skip paths fail to validate declared field types against the real data. A mismatched schema can therefore trigger type confusion and out-of-bounds memory access.
Rust and zero-copy Java
CVE-2026-60080 is a use-after-free in Rust deserialization logic. A crafted payload could crash the process or disclose memory. Meanwhile, CVE-2026-64609 allows an out-of-bounds read via sun.misc.Unsafe. It only affects out-of-band zero-copy deserialization, which is opt-in. Applications not using that feature are safe from it.
Affected versions
The Java flaws reach back to 0.5.0. The C++ bug starts at 0.14.0, and the Rust bug covers 0.13.0 through 1.3.0. Watch the rename, since builds before 0.11.0 shipped as org.apache.fury:fury-core. Newer builds use org.apache.fory:fory-core.
Patch steps
Upgrade to Fory 1.4.0, which resolves all four issues. Grab it from the official Apache Fory download page. Also check transitive dependencies, since Fory often ships inside other tools. No public exploit or in-the-wild abuse has been confirmed. Even so, patching these Apache Fory vulnerabilities early is the safer path.
Support Our Threat Intelligence
If you find our CVE report and cybersecurity news helpful, consider supporting our work.