CVE-2025-32897: Deserialization of Untrusted Data vulnerability in Apache Seata (incubating). This security vulnerability is

Q: How do I fix CVE-2025-32897?

seata: upgrade to 2.3.0. Exact commands for each OS are on this page.

Q: Is CVE-2025-32897 being exploited?

CVE-2025-32897 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2025-32897 affect?

CVE-2025-32897 affects seata. Severity is critical (CVSS 9.8). 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 Apa

Q: How urgent is CVE-2025-32897?

Priority 68/100. Critical severity; CISA SSVC: automatable with total technical impact; Remotely exploitable, no login, no user action; On your watchlist

This week

CRITICAL 9.8REMOTEWATCHLISTUPGRADE

CVE-2025-32897 is a critical-severity flaw (CVSS 9.8) affecting seata. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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. Firs

Why this priority

Critical severity
CISA SSVC: automatable with total technical impact
Remotely exploitable, no login, no user action
On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	2.0% (top 19%)
CISA exploited list	No
Weakness	CWE-502
Published	2025-06-28
Last modified	2026-06-17

Publisher (CNA): Apache Software Foundation · Vendor: apache

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2025-06-28 19:15 UTCPublished CVE record published
2026-06-17 09:12 UTCUpdated Record last modified

apache seata UPGRADE

Affected: >= 2.0.0 and < 2.3.0

Fixed in: 2.3.0

Safe to downgrade to: a release before 2.0.0

1. Check installed version

apt-cache policy seata || rpm -q seata || seata --version

2. UPGRADE to 2.3.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade seata

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade seata

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 2.0.0 (Debian / Ubuntu)

apt-cache madison seata sudo apt install seata=<VERSION_BEFORE_2.0.0> sudo apt-mark hold seata

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list seata sudo dnf downgrade seata-<VERSION_BEFORE_2.0.0> sudo dnf versionlock add seata

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Exact fixes by distribution

Maven · org.apache.seata:seata-config-core · FIXED · 2.3.0 · vulnerable: >= 2.0.0, < 2.3.0 · source

Set org.apache.seata:seata-config-core to 2.3.0 or later in pom.xml or build.gradle, then rebuild and redeploy.

Fedora ELN · fips-provider-next · FIXED · 1.5.3-3.eln159 · FEDORA-2026-3ce99ec7df · source

sudo dnf upgrade --advisory=FEDORA-2026-3ce99ec7df

Fedora 46 · rubygem-webmock · FIXED · 3.26.1-3.fc46 · FEDORA-2026-bb57b4d095 · source

sudo dnf upgrade --advisory=FEDORA-2026-bb57b4d095

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-32897?

seata: upgrade to 2.3.0. Exact commands for each OS are on this page.

Is CVE-2025-32897 being exploited?

CVE-2025-32897 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-32897 affect?

CVE-2025-32897 affects seata. Severity is critical (CVSS 9.8). 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 Apa

How urgent is CVE-2025-32897?

Priority 68/100. Critical severity; CISA SSVC: automatable with total technical impact; Remotely exploitable, no login, no user action; On your watchlist

Related CVEs

CVE-2025-53606 CRITICAL 9.8 DOWNGRADE Deserialization of Untrusted Data vulnerability in Apache Seata (incubating). This issue affects Apache Seata
CVE-2024-54016 MEDIUM 4.3 UPGRADE Improper Handling of Highly Compressed Data (Data Amplification) vulnerability in Apache Seata (incubating).
CVE-2024-47552 CRITICAL 9.8 UPGRADE Deserialization of Untrusted Data vulnerability in Apache Seata (incubating). This issue affects Apache S
CVE-2024-22399 CRITICAL 9.8 UPGRADE Deserialization of Untrusted Data vulnerability in Apache Seata. When developers disable authentication on t

References

← Back to latest CVEs