cve.bz

CVE-2020-5413 Deserialization of Untrusted Data

9.8 criticalEPSS 4.4%Fix available

Critical (9.8). EPSS 4.4% estimated probability of exploitation activity in the next 30 days. Fixed in org.springframework.integration:spring-integration-core 4.3.23, 5.1.12, 5.2.8.

On this page
Spring Integration framework provides Kryo Codec implementations as an alternative for Java (de)serialization. When Kryo is configured with default options, all unregistered classes are resolved on demand. This leads to the "deserialization gadgets" exploit when provided data contains malicious code for execution during deserialization. In order to protect against this type of attack, Kryo can be configured to require a set of trusted classes for (de)serialization. Spring Integration should be proactive against blocking unknown "deserialization gadgets" when configuring Kryo in code.

Severity

CVSS 3.1

9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
4.4% (unchanged from 4.4% a week ago; 4.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 92nd percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-502 Deserialization of Untrusted Data
OWASP Top 10
A08:2025 Software or Data Integrity Failures
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2020-5413 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2020-5413?via=ask-ai-copy and https://cve.bz/cve/CVE-2020-5413?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2020-5413 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Spring by VMware Spring Integrationfrom 4.3 before v4.3.23.RELEASE
Spring by VMware Spring Integrationfrom 5.1 before v5.1.12.RELEASE
Spring by VMware Spring Integrationfrom 5.2 before v5.2.8.RELEASE
Spring by VMware Spring Integrationfrom 5.3 before v5.3.2.RELEASE

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-86qr-9vqc-pgc6Mavenorg.springframework.integration:spring-integration-core>=4.3.0 <4.3.234.3.23
GHSA-86qr-9vqc-pgc6Mavenorg.springframework.integration:spring-integration-core>=5.3.0 <5.3.25.3.2
GHSA-86qr-9vqc-pgc6Mavenorg.springframework.integration:spring-integration-core>=5.1.0 <5.1.125.1.12
GHSA-86qr-9vqc-pgc6Mavenorg.springframework.integration:spring-integration-core>=5.2.0 <5.2.85.2.8

Attack patterns (CAPEC)

  • CAPEC-586 Object Injection Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON