Skip to main content
VulnerabilityPublished Updated

CVE-2024-47552: Apache Seata (incubating) · Deserialization of Untrusted Data

Affects Apache Seata (incubating)Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical · fixed in 2.2.0 : patch Apache Seata (incubating) as a priority.

Data as of 26 Oct 2026, 12:54 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.2% chance of exploitation in 30 days – higher than 69% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.2.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Mar 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Mavenorg.apache.seata/seatapkg:maven/org.apache.seata/seataOther threatsAffected
  • =2.0.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Organizations should immediately upgrade Apache Seata to version 2.2.0 or later, where this vulnerability is fixed. Until upgrading, restrict network access to the Raft cluster mode components strictly to trusted hosts and segments, employing network segmentation and firewall rules to limit exposure. Monitor internal network traffic for unusual serialized data exchanges or unexpected connections to Seata nodes. Implement strict access controls and authentication mechanisms for internal services to reduce the risk of unauthorized access. Conduct regular audits and vulnerability scans focusing on middleware components. Additionally, consider disabling the Raft cluster mode if not required, reverting to the traditional architecture which is unaffected. Employ runtime application self-protection (RASP) or endpoint detection and response (EDR) solutions to detect anomalous behavior indicative of exploitation attempts. Maintain up-to-date backups and incident response plans to quickly recover from potential compromises.

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

Community reviews

Loading reviews…