ForyApplication · Apache
CVE-2025-59328
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 · uneditedA vulnerability in Apache Fory allows a remote attacker to cause a Denial of Service (DoS). The issue stems from the insecure deserialization of untrusted data. An attacker can supply a large, specially crafted data payload that, when processed, consumes an excessive amount of CPU resources during the deserialization process. This leads to CPU exhaustion, rendering the application or system using the Apache Fory library unresponsive and unavailable to legitimate users. Users of Apache Fory are strongly advised to upgrade to version 0.12.2 or later to mitigate this vulnerability. Developers of libraries and applications that depend on Apache Fory should update their dependency requirements to Apache Fory 0.12.2 or later and release new versions of their software.
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 confidenceApache Fory versions before 0.12.2 contain an insecure deserialization vulnerability where processing a specially crafted large data payload causes excessive CPU consumption during deserialization, leading to denial of service. A remote attacker can exploit this by sending malicious data to any Fory endpoint that performs deserialization.
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
>= 0.5.0, < 0.12.2CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Apache Fory versionCheck your project dependencies (Maven pom.xml, Gradle build.gradle, or library manifests) for the Apache Fory version, or inspect the fory-core jar file metadata if running directly. Run: mvn dependency:tree | grep fory or check your package manager.Affected if The version is 0.5.0 or higher but below 0.12.2
-
Identify deserialization endpointsReview your Fory application code and configuration for endpoints or handlers that accept and deserialize incoming data (such as RPC calls, event processing, or data ingestion points). Search for deserialization-related classes or serializers in your codebase.Affected if Your application exposes any Fory endpoints that perform deserialization of external data
-
Check network exposure of deserialization handlersReview network configuration and firewall rules to determine whether Fory deserialization endpoints are accessible from untrusted networks or the internet. Check your service listener bindings and exposed ports.Affected if Deserialization endpoints are reachable from external networks without authentication or network filtering
-
Audit existing payload processing logsReview application logs for patterns of unusually high CPU usage correlated with deserialization operations, or monitor for slow deserialization processing times that may indicate exploitation attempts.Affected if You observe abnormal CPU spikes during deserialization or unusually long processing times for incoming data payloads
You are affected if Apache Fory version is 0.5.0 to 0.12.1 and your environment uses accessible deserialization endpoints that process external data.
Generated from the published advisory. Verify against your own configuration.
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 · scoped0.12.2
Upgrade Apache Fory dependency to version 0.12.2 or later in all applications and libraries that depend on it. This addresses the insecure deserialization vulnerability that allows CPU exhaustion attacks.
Apache Fory 0.12.2
- Identify the current version of Apache Fory in use by checking project dependencies (Maven pom.xml, Gradle build.gradle, or similar)
- Update the dependency configuration to require Apache Fory version 0.12.2 or later (e.g., change version constraint from <0.12.2 to >=0.12.2)
- Run the dependency management update command (e.g., mvn update for Maven, ./gradlew dependencies for Gradle)
- Rebuild the application to incorporate the fixed library version
- Verify the application functions correctly with the updated dependency
- Deploy the rebuilt application to production
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Fory
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-59328 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-59328 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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