Apache Fory Deserialization Flaw Lets Attackers Bypass Java Safety Checks
Apache disclosed CVE-2026-50076, an important- to high-severity deserialization vulnerability in the Java SDK of Apache Fory that affects org.apache.fory:fory-core versions before 1.1.0. The flaw lies in the Java ReplaceResolverSerializer replace-resolve path, where incomplete verification allows crafted Fory serialized data to bypass class registration requirements, TypeChecker enforcement, and DisallowedList protections during deserialization.
If an application processes untrusted external data streams, a remote attacker can trigger classpath-present readResolve and readExternal hooks on Java/JVM systems, creating a path to unauthorized code execution on backend servers. Apache fixed the issue in version 1.1.0 by adding stricter sanitization checks before deserialization and advised users to upgrade immediately and review deployments that deserialize externally supplied data; the vulnerability was reported by Venkatraman Kumar (r3dw0lfsec) of Securin.

Get ahead of threats like this
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
How this story unfolded
2 events from the most recent confirmed update back to the earliest known activity.
Apache Fory 1.1.0 released to fix CVE-2026-50076
Apache Fory maintainers released version 1.1.0 or later as the remediation for CVE-2026-50076. The fix adds stricter sanitization checks before deserialization to prevent the ReplaceResolverSerializer bypass.
Apache discloses CVE-2026-50076 in Apache Fory Java SDK
Apache disclosed CVE-2026-50076, an important-severity deserialization vulnerability in the Java replace-resolve path of fory-core that can let crafted serialized data bypass class registration, TypeChecker, and DisallowedList protections. The issue was credited to Venkatraman Kumar (r3dw0lfsec) of Securin.
Related entities
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
Sources
2 references tracked. Mallory keeps watching after this page renders.
See the full picture, correlated to your attack surface.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.


