Users are recommended to upgrade to version 1.1.0 or later, which fixes this issue.
Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Mon, 08 Jun 2026 13:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:apache:fory:*:*:*:*:*:*:*:* |
Fri, 05 Jun 2026 10:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Apache
Apache fory |
|
| Vendors & Products |
Apache
Apache fory |
Thu, 04 Jun 2026 18:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
Thu, 04 Jun 2026 17:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
cvssV3_1
|
Thu, 04 Jun 2026 16:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Deserialization of Untrusted Data in the Java replace-resolve path in Apache Fory fory-core Java SDK before 1.1.0 on Java/JVM platforms allows a remote attacker to bypass class registration, TypeChecker, and DisallowedList checks and invoke classpath-present readResolve/readExternal hooks via crafted Fory serialized data. Users are recommended to upgrade to version 1.1.0 or later, which fixes this issue. | |
| Title | Apache Fory: Java ReplaceResolverSerializer deserialization checks bypass | |
| Weaknesses | CWE-502 | |
| References |
|
Status: PUBLISHED
Assigner: apache
Published:
Updated: 2026-06-04T17:01:57.229Z
Reserved: 2026-06-03T12:46:29.360Z
Link: CVE-2026-50076
Updated: 2026-06-04T17:01:57.229Z
Status : Analyzed
Published: 2026-06-04T17:16:33.390
Modified: 2026-06-08T13:00:55.350
Link: CVE-2026-50076
No data.
OpenCVE Enrichment
Updated: 2026-06-05T10:07:27Z