Vulnerabilities in pkg:maven/org.apache.seata/seata-config-core
PACKAGECVE-2025-32897 is a LOW apache seata vulnerable to deserialization vulnerability (CWE-502: Deserialization of Untrusted Data) affecting Seata config core libraries in the Maven ecosystem. The issue involves apache seata vulnerable to deserialization of untrusted data. Remediation is available by upgrading affected packages to version 2.3.0.
pkg:maven/org.apache.seata/seata-config-core
Vulnerability advisories affecting package pkg:maven/org.apache.seata/seata-config-core. Select an advisory below to view technical details or fixes.
| Advisory ID | CVE / NVD | Severity | Summary |
|---|---|---|---|
| GHSA-m964-fjrh-xxq2 | CVE-2025-32897 | LOW | Apache Seata Vulnerable to Deserialization of Untrusted Data |
| GHSA-2r4x-667f-mpfh | CVE-2024-47552 | LOW | Apache Seata Vulnerable to Deserialization of Untrusted Data |
CVE-2025-32897 at a Glance
How to Fix CVE-2025-32897
To remediate this vulnerability, upgrade all affected Seata config core dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
<dependency>
<groupId>org.apache.seata</groupId>
<artifactId>seata-config-core</artifactId>
<version>2.3.0</version>
</dependency>Run the following command in your project directory to verify that all resolved dependencies use the patched release:
mvn dependency:tree -Dincludes=org.apache.seataHow to Check if You Are Affected
To determine whether your Java application is affected by CVE-2025-32897, inspect your build dependencies using the Maven Dependency Plugin:
mvn dependency:tree -Dincludes=org.apache.seataAnalyze the terminal output to locate any version of Seata config core in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.3.0), your application is affected.
Note: The mvn dependency:tree -Dincludes=org.apache.seata command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-502: Deserialization of Untrusted Data, where the product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid. In Seata config core, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2025-32897 Affected Seata config core Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
org.apache.seata:seata-config-core
|
Maven |
≥ 2.0.0
< 2.3.0
|
2.3.0
|
References
Frequently Asked Questions
What is CVE-2025-32897?
Which Seata config core versions are affected?
What version fixes CVE-2025-32897?
Is seata-config-core affected?
What CWE is associated with CVE-2025-32897?
How can I check Maven dependencies for CVE-2025-32897?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-m964-fjrh-xxq2",
"modified" : "2026-03-30T20:30:52Z",
"published" : "2025-06-28T21:30:27Z",
"aliases" : [ "CVE-2025-32897" ],
"summary" : "Apache Seata Vulnerable to Deserialization of Untrusted Data",
"details" : "Deserialization of Untrusted Data vulnerability in Apache Seata (incubating).\n\nThis security vulnerability is the same as CVE-2024-47552, but the version range described in the CVE-2024-47552 definition is too narrow.\nThis issue affects Apache Seata (incubating): from 2.0.0 before 2.3.0.\n\nThe 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.\n\nUsers are recommended to upgrade to version 2.3.0, which fixes the issue.",
"severity" : [ ],
"affected" : [ {
"package" : {
"ecosystem" : "Maven",
"name" : "org.apache.seata:seata-config-core"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "2.0.0"
}, {
"fixed" : "2.3.0"
} ]
} ]
} ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-32897"
}, {
"type" : "WEB",
"url" : "https://github.com/apache/incubator-seata/commit/20cd9625d23f99b71fefc83b8db96c14092a9950"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/apache/incubator-seata"
}, {
"type" : "WEB",
"url" : "https://lists.apache.org/thread/9fhtf7yvpjpzlwd1m0wfgg6tp2btxpy1"
}, {
"type" : "WEB",
"url" : "https://www.cve.org/CVERecord?id=CVE-2024-47552"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-502" ],
"severity" : "LOW",
"github_reviewed" : true,
"github_reviewed_at" : "2025-06-30T21:09:11Z",
"nvd_published_at" : "2025-06-28T19:15:21Z"
}
}