CVE-2025-53606 Apache Seata (incubating): Deserialization of untrusted Data in Apache Seata Server
Critical 9.8
Published
Updated
Check this codebase for CVE-2025-53606 and fix it if it is affected.
What it is: CVE-2025-53606 is a critical vulnerability in Apache Seata (incubating), published on 8 Aug 2025.
Exploitation: There is no known exploitation of CVE-2025-53606 in the wild and no public exploit code.
Affected packages and fixed versions:
- org.apache.seata:seata-serializer-fury (Maven): affected from 2.4.0; fixed in 2.5.0
- org.apache.seata:seata-serializer-fury (Maven): affected from 2.4.0; fixed in 2.5.0
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2025-53606/ (Markdown: https://insights.sbomify.com/CVE-2025-53606/index.md)
- Exploited in the wild
- Not known
- Fix
- Available
What is CVE-2025-53606?
CVE-2025-53606 is a critical vulnerability in Apache Seata (incubating), published on 8 Aug 2025.
Official 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.
Weakness: CWE-502
Which versions are affected by CVE-2025-53606?
2 open source packages ship an affected version, including org.apache.seata:seata-serializer-fury. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
org.apache.seata:seata-serializer-fury Maven | From 2.4.0 | 2.5.0 |
org.apache.seata:seata-serializer-fury Maven | From 2.4.0 | 2.5.0 |
Products include Apache Seata.
How do I fix CVE-2025-53606?
Upgrade org.apache.seata:seata-serializer-fury to 2.5.0 or later.
Is CVE-2025-53606 being exploited?
There is no known exploitation of CVE-2025-53606 in the wild and no public exploit code.
Other vulnerabilities in Apache Seata (incubating)
- CVE-2025-32897 Apache Seata (incubating): Deserialization of untrusted Data in Apache Seata Server
- CVE-2024-47552 Apache Seata (incubating): Deserialization of untrusted Data in jraft mode in Apache Seata Server
- CVE-2024-22399 Apache Seata: Remote Code Execution vulnerability via Hessian Deserialization in Apache Seata Server
- CVE-2024-54016 compression bomb attack in Apache Seata Server
Sources
Also known as GHSA-g358-g2pq-c46j.