GHSA-g358-g2pq-c46j — seata-serializer-fury
Fix: apache/incubator-seata@d2a18aeGHSA-g358-g2pq-c46j is a Deserialization of Untrusted Data vulnerability in org.apache.seata:seata-serializer-fury. A fix is available for org.apache.seata:seata-serializer-fury — see the affected versions and patch details below.
Apache Seata: Deserialization of untrusted Data in Apache Seata Server
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-g358-g2pq-c46j.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Real-World Exposure
org.apache.seata:seata-serializer-furyReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.seata:seata-serializer-fury | ≥ 2.4.0&&< 2.5.0 | 2.5.0org.apache.seata:seata-serializer-fury:2.5.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.seata:seata-serializer-fury, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.seata:seata-serializer-fury to 2.5.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g358-g2pq-c46j is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-g358-g2pq-c46j can be triaged on real exposure rather than presence alone.
Tailored to GHSA-g358-g2pq-c46j. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-g358-g2pq-c46j in your dependencies?
O3 Security finds GHSA-g358-g2pq-c46j across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.