Apache Seata security advisories

Security information for Apache Seata

Reporting

Do you want disclose a potential security issue for Apache Seata? You can read more about the projects’ security policy on their security page, and email your report to the Apache Security Team.

Advisories

This section is experimental: it provides advisories since 2023 and may lag behind the official CVE publications. It may also lack details found on the project security page. If you have any feedback on how you would like this data to be provided, you are welcome to reach out on our public mailinglist or privately on security@apache.org

Deserialization of untrusted Data in Apache Seata Server

CVE-2025-53606 [CVE] [CVE json] [OSV json]

Last updated: 2025-08-08T09:22:52.076Z

Affected

  • Apache Seata (incubating) at 2.4.0

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.

References

Credits

  • A.R. (finder)

Deserialization of untrusted Data in Apache Seata Server

CVE-2025-32897 [CVE] [CVE json] [OSV json]

Last updated: 2026-03-30T02:05:32.515Z

Affected

  • Apache Seata (incubating) from 2.0.0 before 2.3.0

Description

Deserialization of Untrusted Data vulnerability in Apache Seata (incubating).

This security vulnerability is the same as CVE-2024-47552, but the version range described in the CVE-2024-47552 definition is too narrow.

This issue affects Apache Seata (incubating): from 2.0.0 before 2.3.0.

Severity Justification:
The Apache Seata security team assesses the severity of this vulnerability as "Low" due to stringent real-world mitigating factors. First, the vulnerability is strictly isolated to the Raft cluster mode, an optional and non-default feature introduced in v2.0.0, while most users rely on the unaffected traditional architecture. Second, Seata is an internal middleware; communication between TC and RM/TM occurs entirely within trusted internal networks. An attacker would require prior, unauthorized access to the Intranet to exploit this, making external exploitation highly improbable.

Users are recommended to upgrade to version 2.3.0, which fixes the issue.

References

compression bomb attack in Apache Seata Server

CVE-2024-54016 [CVE] [CVE json] [OSV json]

Last updated: 2025-03-20T08:59:24.157Z

Affected

  • Apache Seata (incubating) through <=2.2.0

Description

Improper Handling of Highly Compressed Data (Data Amplification) vulnerability in Apache Seata (incubating).

This issue affects Apache Seata (incubating): through <=2.2.0.

Users are recommended to upgrade to version 2.3.0, which fixes the issue.

References

Credits

Deserialization of untrusted Data in jraft mode in Apache Seata Server

CVE-2024-47552 [CVE] [CVE json] [OSV json]

Last updated: 2026-03-30T02:08:11.034Z

Affected

  • Apache Seata (incubating) from 2.0.0 before 2.2.0

Description

Deserialization of Untrusted Data vulnerability in Apache Seata (incubating).

This issue affects Apache Seata (incubating): from 2.0.0 before 2.2.0.

Severity Justification:
The Apache Seata security team assesses the severity of this vulnerability as "Low" due to stringent real-world mitigating factors. First, the vulnerability is strictly isolated to the Raft cluster mode, an optional and non-default feature introduced in v2.0.0, while most users rely on the unaffected traditional architecture. Second, Seata is an internal middleware; communication between TC and RM/TM occurs entirely within trusted internal networks. An attacker would require prior, unauthorized access to the Intranet to exploit this, making external exploitation highly improbable.

Users are recommended to upgrade to version 2.2.0, which fixes the issue.

References

Credits

Remote Code Execution vulnerability via Hessian Deserialization in Apache Seata Server

CVE-2024-22399 [CVE] [CVE json] [OSV json]

Last updated: 2024-09-16T11:42:03.440Z

Affected

  • Apache Seata at 2.0.0
  • Apache Seata from 1.0.0 through 1.8.0

Description

Deserialization of Untrusted Data vulnerability in Apache Seata. 

When developers disable authentication on the Seata-Server and do not use the Seata client SDK dependencies, they may construct uncontrolled serialized malicious requests by directly sending bytecode based on the Seata private protocol.

This issue affects Apache Seata: 2.0.0, from 1.0.0 through 1.8.0.

Users are recommended to upgrade to version 2.1.0/1.8.1, which fixes the issue.


References

Credits