CVE-2025-32897
Last modified
CVE-2025-32897 is a critical-severity vulnerability rated 9.8/10 on the CVSS scale. 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. EPSS estimates a 1.68% chance of exploitation in the next 30 days.
Description
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.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Apache | Seata | >= 2.0.0, < 2.3.0 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2025-32897?
How severe is CVE-2025-32897?
How do I fix CVE-2025-32897?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2025
- CVE-2025-32887An issue was discovered on goTenna v1 devices with app 5.5.3…6.5
- CVE-2025-32888An issue was discovered on goTenna Mesh devices with app 5.5…8.8
- CVE-2025-32889An issue was discovered on goTenna v1 devices with app 5.5.3…8.8
- CVE-2025-3289A local code execution vulnerability exists in the Rockwell …7.8
- CVE-2025-32890An issue was discovered on goTenna Mesh devices with app 5.5…6.5
- CVE-2025-32896# Summary Unauthorized users can perform Arbitrary File Rea…6.5
- CVE-2025-32898The KDE Connect verification-code protocol before 2025-04-18…4.7
- CVE-2025-32899In KDE Connect before 1.33.0 on Android, a packet can be cra…4.3
- CVE-2025-32900In the KDE Connect information-exchange protocol before 2025…4.3
- CVE-2025-32901In KDE Connect before 1.33.0 on Android, malicious device ID…4.3
- CVE-2025-32906A flaw was found in libsoup, where the soup_headers_parse_re…7.5
- CVE-2025-32907A flaw was found in libsoup. The implementation of HTTP rang…5.3
Are you affected by CVE-2025-32897?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
