Skip to content
Fencer Vulns
critical 9.8

CVE-2024-47552 json

Apache Seata (incubating): Deserialization of untrusted Data in jraft mode in Apache Seata Server

published 2025-03-20 19 mo ago modified 2026-06-17 4 mo ago also GHSA-2r4x-667f-mpfh , EUVD-2025-6743

cvss
9.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.2%
EPSS 1.2% chance of exploitation in 30 days, percentile 69%
public exploits
0
none known

Summary

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.

Patch / fix

  • maven org.apache.seata:seata-config-core 2.2.0
  • Apache Software Foundation Apache Seata (incubating) 2.2.0

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
total
Assessed
19 mo ago

Exploit prediction

1.25% chance of exploitation in the next 30 days, higher than 69% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CISA ADP 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
maven org.apache.seata:seata-config-core
>=2.0.0, <2.2.0
2.2.0

Affected products

  • Apache Software Foundation Apache Seata (incubating)

Classification

Weakness
  • CWE-502 Deserialization of Untrusted Data

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.