Skip to main content
VulnerabilityPublished Updated

CVE-2025-53606: Apache Seata (incubating) · Deserialization of Untrusted Data

Affects Apache Seata (incubating)Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical · fixed in 2.5.0 : patch Apache Seata (incubating) as a priority.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.7% chance of exploitation in 30 days – higher than 53% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.5.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Aug 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Apache Software Foundation Apache Seata (incubating)Affected
  • =2.4.0
Fixed in–

AI-suggested

  1. Immediate upgrade to Apache Seata version 2.5.0 or later, which contains the fix for this vulnerability.
  2. Restrict network access to Apache Seata services using firewalls or network segmentation to limit exposure to untrusted networks.
  3. Implement strict input validation and monitoring on endpoints handling serialized data to detect anomalous payloads.
  4. Employ runtime application self-protection (RASP) or endpoint detection and response (EDR) solutions to identify and block exploitation attempts.
  5. Regularly audit and review distributed transaction configurations and logs for suspicious activities.
  6. Educate development and operations teams about secure deserialization practices and the risks associated with untrusted data.
  7. Consider deploying Web Application Firewalls (WAFs) with custom rules to detect and block malicious serialized payloads targeting Seata endpoints.
  8. Maintain an incident response plan tailored to handle potential exploitation of deserialization vulnerabilities.

Description

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.

References

Community reviews

Loading reviews…