CVE-2026-60080 Apache Fory: Rust MetaString heap use-after-free
High 7.3
Published
Updated
Check this codebase for CVE-2026-60080 and fix it if it is affected.
What it is: CVE-2026-60080 is a high-severity vulnerability in Apache Fory, published on 21 Jul 2026.
Exploitation: There is no known exploitation of CVE-2026-60080 in the wild and no public exploit code.
Affected product: Apache Fory. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2026-60080/ (Markdown: https://insights.sbomify.com/CVE-2026-60080/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-60080?
CVE-2026-60080 is a high-severity vulnerability in Apache Fory, published on 21 Jul 2026.
Official description
Use After Free vulnerability in the Rust deserialization logic of Apache Fory. This issue affects Apache Fory from 0.13.0 through 1.3.0.
A crafted Fory payload could cause undefined behavior, process crash, or potential memory disclosure.
Users are recommended to upgrade to version 1.4.0, which fixes the issue.
Weakness: CWE-416
Which versions are affected by CVE-2026-60080?
It affects 1 product.
Products include Apache Fory.
How do I fix CVE-2026-60080?
No fix has been published for CVE-2026-60080 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-60080 being exploited?
There is no known exploitation of CVE-2026-60080 in the wild and no public exploit code.
Other vulnerabilities in Apache Fory
- CVE-2026-71558 Apache Fory: Heap type confusion in C++ polymorphic smart-pointer deserialization
- CVE-2026-64606 Apache Fory, Apache Fory: Class-registration bypass through an auto-admitted SerializedLambda capturing interface
- CVE-2026-64608 Apache Fory: Heap type confusion and out-of-bounds read/write in C++ compatible-mode field-skip paths
- CVE-2026-48207 Apache Fory: PyFory ReduceSerializer Incomplete Policy Enforcement
- CVE-2025-61622 Apache Fory, Apache Fory: Python RCE via unguarded pickle fallback serializer in pyfory
Sources
Also known as GHSA-8g3p-5q43-955w.