dbcve.org
SeataApplication · Apache

CVE-2025-32897

CRITICAL · 9.8 CVSS v3.1 Published 2025-06-28
Fix available
A fix is available. Upgrade to 2.3.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is a deserialization of untrusted data vulnerability in Apache Seata, affecting the Raft cluster mode (an optional feature introduced in v2.0.0). The vulnerability allows an attacker with access to the internal network to potentially execute arbitrary code through malicious serialized data. This CVE expands the affected version range from the earlier CVE-2024-47552.

MitigationUpgrade Apache Seata to version 2.3.0 or later. If upgrading is not immediately possible, disable Raft cluster mode and ensure network isolation since exploitation requires access to the internal network.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SeataApplication
Affected:>= 2.0.0, < 2.3.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Seata installation and version
    Locate the Seata installation directory and check for version information in release files, startup scripts, or configuration metadata. Common locations include the root Seata directory or embedded version properties within the Seata JAR files.
    Affected if The installed version is 2.0.0, 2.1.x, or 2.2.x (any version >= 2.0.0 and < 2.3.0)
  2. Confirm Raft cluster mode is in use
    Inspect the Seata configuration files (such as seata.conf or application.yml/properties) for Raft-specific cluster settings. Look for Raft-related parameters such as cluster mode configuration pointing to Raft, Raft server addresses, or Raft-specific registry settings.
    Affected if Raft cluster mode is explicitly configured or enabled in the Seata configuration
  3. Verify network exposure of Seata service
    Review network binding configuration to determine if Seata server ports (default 8091 for transaction service, and Raft-specific ports) are exposed to untrusted networks or external interfaces rather than restricted to localhost or trusted internal networks.
    Affected if Seata is listening on interfaces accessible from untrusted networks (0.0.0.0 or public IP bindings)

You are affected if Seata version is between 2.0.0 and 2.2.x inclusive AND Raft cluster mode is enabled, with the service exposed to untrusted networks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.3.0 or later
Fixed in 2.3.0
Vendor patch github.com →
Interim mitigation

Upgrade Apache Seata to version 2.3.0 or later. If upgrading is not immediately possible, disable Raft cluster mode and ensure network isolation since exploitation requires access to the internal network.

Recommended fix High confidence

2.3.0

  1. 1. Back up your current Seata configuration, scripts, and any persistent data before proceeding
  2. 2. Download Apache Seata version 2.3.0 from the official Apache Seata release repository (https://github.com/apache/incubator-seata/releases)
  3. 3. In a non-production environment, test the upgrade to ensure compatibility with your existing RM/TM (Resource Manager/Transaction Manager) clients
  4. 4. Upgrade the Seata Server (TC) components to version 2.3.0
  5. 5. If using Raft cluster mode, ensure all Raft cluster nodes are upgraded to version 2.3.0
  6. 6. Verify the upgrade by checking that the Seata server starts successfully and accepts connections from your clients
  7. 7. Monitor logs for any deserialization-related errors or warnings after the upgrade
Caveat Review the Seata 2.3.0 release notes for any configuration or API changes from your current version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Seata Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,080
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,928.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-32897 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-32897 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data