CVE-2025-53606 is a critical-severity (CVSS 9.8) Deserialization of Untrusted Data vulnerability in org.apache.seata:seata-serializer-fury. A fix is available for org.apache.seata:seata-serializer-fury — see the affected versions and patch details below.
Apache Seata (incubating): Deserialization of untrusted Data in Apache Seata Server
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-53606.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.apache.seata:seata-serializer-furyReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Deserialization of Untrusted Data vulnerability in Apache Seata (incubating).
This issue affects Apache Seata (incubating): 2.4.0.
Users are recommended to upgrade to version 2.5.0, which fixes the issue.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.seata:seata-serializer-fury | ≥ 2.4.0&&< 2.5.0 | 2.5.0org.apache.seata:seata-serializer-fury:2.5.0 |
Affected Products
seataapacheDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.seata:seata-serializer-fury, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.seata:seata-serializer-fury to 2.5.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-53606 is resolved across your whole dependency graph.
Workarounds
Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.
Frequently Asked Questions
Is CVE-2025-53606 in your dependencies?
Find it across Maven, including transitive dependencies.