Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2024-22399: Deserialization of Untrusted Data vulnerability in Apache Seata.  When developers disable authentication on t

66
This week
CRITICAL 9.8REMOTEWATCHLISTUPGRADE

CVE-2024-22399 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.  When developers disable authentication on the Seata-Server and do not use the Seata client SDK dependencies, they may construct uncontrolled serialized malicious requests by directly sending bytecode based on the Seata private protocol. This issue affects Apache Seata: 2.0.0, from 1.0.0 through 1.8.0. Users are recommended to upgrade to version 2.1.0/1.8.1, which fixes the issue

Why this priority

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

A fixed release or distro patch exists.

Risk facts

CVSS score9.8 (Critical)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance3.3% (top 12%)
CISA exploited listNo
WeaknessCWE-502
Published2024-09-16
Last modified2026-06-17
Publisher (CNA): Apache Software Foundation · Vendor: apache

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

apache seata UPGRADE
Affected: >= 1.0.0 and < 1.8.1 · 2.0.0
Fixed in: 1.8.1
Safe to downgrade to: a release before 1.0.0
1. Check installed version
apt-cache policy seata || rpm -q seata || seata --version
2. UPGRADE to 1.8.1 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade seata
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade seata
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 1.0.0 (Debian / Ubuntu)
apt-cache madison seata sudo apt install seata=<VERSION_BEFORE_1.0.0> sudo apt-mark hold seata
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list seata sudo dnf downgrade seata-<VERSION_BEFORE_1.0.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-2024-22399?

seata: upgrade to 1.8.1. Exact commands for each OS are on this page.

Is CVE-2024-22399 being exploited?

CVE-2024-22399 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-2024-22399 affect?

CVE-2024-22399 affects seata. Severity is critical (CVSS 9.8). Deserialization of Untrusted Data vulnerability in Apache Seata.  When developers disable authentication on the Seata-Server and do not use the Seata client SDK dependencies, they may construct uncontrolled serialized malicious requests by

How urgent is CVE-2024-22399?

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

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.