CVE-2026-60080 Apache Software Foundation CVE debrief

Who should care

Users of Apache Fory from version 0.13.0 through 1.3.0 should be aware of this vulnerability and take steps to upgrade to version 1.4.0. This includes operators, platform administrators, vulnerability management teams, and security teams who are responsible for ensuring the security of Apache Fory deployments.

Technical summary

The vulnerability is a Use After Free issue in the Rust deserialization logic of Apache Fory, affecting versions from 0.13.0 through 1.3.0. This could lead to undefined behavior, process crashes, or potential memory disclosure when a crafted Fory payload is processed. The issue is addressed in version 1.4.0. Users of Apache Fory should be aware of this vulnerability and take steps to upgrade to version 1.4.0. Operators, platform administrators, vulnerability management teams, and security teams responsible for ensuring the security of Apache Fory deployments should prioritize upgrading to version 1.4.0 to mitigate potential impacts, including process crashes and memory disclosure, and review compensating controls for exposed systems.

Defensive priority

High priority should be given to upgrading Apache Fory to version 1.4.0, as this vulnerability has the potential to cause significant impact.

Recommended defensive actions

• Upgrade Apache Fory to version 1.4.0
• Review and update affected systems
• Monitor for potential exploitation attempts
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The CVE record was published on 2026-07-21T12:18:58.697Z and was last modified on 2026-07-22T17:16:56.957Z. The NVD entry is currently Undergoing Analysis. This information is based on the provided source corpus and may not reflect the current status. Users should verify the information with the official sources for the most up-to-date details.

Official resources