CVE-2025-53606: Deserialization of Untrusted Data vulnerability in Apache Seata (incubating). This issue affects Apache Seata

This month

CRITICAL 9.8REMOTEWATCHLISTDOWNGRADE

CVE-2025-53606 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 issue affects Apache Seata (incubating): 2.4.0. Users are recommended to upgrade to version 2.5.0, which fixes the issue.

Why this priority

Critical severity
Remotely exploitable, no login, no user action
On your watchlist

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.7% (top 46%)
CISA exploited list	No
Weakness	CWE-502
Published	2025-08-08
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-08-08 10:15 UTCPublished CVE record published
2026-06-17 09:38 UTCUpdated Record last modified

apache seata DOWNGRADE

Affected: 2.4.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 2.4.0

1. Check installed version

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

2. No fixed release: DOWNGRADE to a release before 2.4.0 (Debian / Ubuntu)

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

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list seata sudo dnf downgrade seata-<VERSION_BEFORE_2.4.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.

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-53606?

seata: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2025-53606 being exploited?

CVE-2025-53606 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-53606 affect?

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

How urgent is CVE-2025-53606?

Priority 58/100. Critical severity; Remotely exploitable, no login, no user action; On your watchlist

Related CVEs

CVE-2025-32897 CRITICAL 9.8 UPGRADE Deserialization of Untrusted Data vulnerability in Apache Seata (incubating). This security vulnerability is
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