# Apache Seata: Deserialization of untrusted Data in Apache Seata Server

Advisory record · `GHSA-g358-g2pq-c46j`

- **Identifiers:** `GHSA-g358-g2pq-c46j` · `CVE-2025-53606`
- **State:** Confirmed
- **Severity:** CVSS 9.8 Critical
- **Critical:** Yes: CVSS 9+
- **Weakness (CWE):** [CWE-502](https://cwe.mitre.org/data/definitions/502.html)
- **Tags:** [Insecure deserialization](https://agentprime.io/advisories/tag/deserialization.md)
- **Published:** 8 Aug 2025
- **Updated:** 5 Nov 2025
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 8 Aug 2025, 12:32 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Critical

Critical, because:

- CVSS score 9.8: 9.0 or more.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected packages

- `org.apache.seata:seata-serializer-fury` (Maven): affected `>=2.4.0, <2.5.0`; fixed in `2.5.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Apache Seata's seata-serializer-fury package, versions 2.4.0 up to but not including 2.5.0, contains a deserialization of untrusted data flaw. The source gives few details about how an attacker reaches the vulnerable code or what they can do after exploiting it. Upgrade seata-serializer-fury to version 2.5.0, which fixes the issue.

Written 7 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 9.8 Critical, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`, from ADP (CISA-ADP)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0083, the 58th percentile, on 13 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:09 UTC: First seen by agentprime
- 31 Oct 2026, 15:09 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-g358-g2pq-c46j)

## Sources

- [GitHub Advisory Database: GHSA-g358-g2pq-c46j](https://github.com/advisories/GHSA-g358-g2pq-c46j)
- [OSV: GHSA-g358-g2pq-c46j](https://osv.dev/vulnerability/GHSA-g358-g2pq-c46j)
- <https://nvd.nist.gov/vuln/detail/CVE-2025-53606>
- <https://github.com/apache/incubator-seata/commit/d2a18aef82c08535e4134642070c39d98654f0f6>
- <https://github.com/apache/incubator-seata>
- <https://lists.apache.org/thread/ggfd72vvvxjozs81zbcls45zxg64pphx>
- <http://www.openwall.com/lists/oss-security/2025/08/07/1>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-g358-g2pq-c46j>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-g358-g2pq-c46j/>. Everything for agents: <https://agentprime.io/llms.txt>.