dbcve.org
ForyApplication · Apache

CVE-2026-50076

CRITICAL · 9.1 CVSS v3.1 Published 2026-06-04
Fix available
A fix is available. Upgrade to 1.1.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Apache Fory fory-core Java SDK before 1.1.0 contains a deserialization vulnerability in the Java replace-resolve path that allows remote attackers to bypass security checks (class registration, TypeChecker, and DisallowedList). By crafting malicious Fory serialized data, attackers can invoke classpath-present readResolve and readExternal hooks, potentially achieving remote code execution.

MitigationUpgrade Apache Fory fory-core to version 1.1.0 or later to resolve the deserialization bypass. If upgrading is not immediately feasible, consider disabling or restricting deserialization of untrusted data and implementing additional network-level controls.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ForyApplication
Affected:< 1.1.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify fory-core dependency
    Examine your project's dependency management file (Maven pom.xml, Gradle build.gradle, or similar) or list all JAR files in the classpath to locate fory-core. Search for any JAR with 'fory-core' in the filename.
    Affected if fory-core is present in the project dependencies or classpath
  2. Determine installed fory-core version
    Check the version of fory-core by inspecting the JAR manifest (META-INF/MANIFEST.MF), the dependency declaration in your build file, or by running: jar -xf fory-core.jar META-INF/MANIFEST.MF && cat META-INF/MANIFEST.MF
    Affected if The version is lower than 1.1.0 or the version cannot be determined (indicating an older release)
  3. Verify deserialization is in use
    Search your codebase for usage of Fory serialization classes such as FstSerializer, KryoSerializer, FstObjectInputStream, or any Fory-based deserialization configuration. Also check configuration files for serializer registrations.
    Affected if The application uses Fory's deserialization features to serialize/deserialize Java objects
  4. Confirm security configuration exists
    Inspect the application for security-related configuration involving TypeChecker, DisallowedList, or class registration whitelists used with Fory deserializers. These are the security mechanisms that can be bypassed.
    Affected if Security checks (TypeChecker, DisallowedList, or class whitelists) are configured for Fory deserialization

You are affected if fory-core version is present and is below 1.1.0 AND your application uses Fory's deserialization features, regardless of whether security checks are configured (they can be bypassed).

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.1.0 or later
Fixed in 1.1.0
Interim mitigation

Upgrade Apache Fory fory-core to version 1.1.0 or later to resolve the deserialization bypass. If upgrading is not immediately feasible, consider disabling or restricting deserialization of untrusted data and implementing additional network-level controls.

Recommended fix High confidence

1.1.0

  1. Locate all build configuration files (pom.xml, build.gradle, build.gradle.kts, or similar) that contain the Fory fory-core dependency
  2. Update the Fory fory-core dependency version from the current version to 1.1.0 or later (e.g., change <version> to 1.1.0)
  3. Verify all other Fory-related dependencies are also updated to version 1.1.0 or later to maintain consistency
  4. Run Maven or Gradle dependency resolution to confirm the new version is available
  5. Rebuild the entire application to ensure compatibility with the updated library
  6. Run existing test suites, particularly any tests related to serialization/deserialization functionality
  7. Deploy the rebuilt application to your production environment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Fory Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-50076 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-50076 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data