NVD / CVE Program· CNA pivotal

CVE-2020-5413: Kryo Configuration Allows Code Execution with Unknown "Serialization Gadgets"

Noroxi assessment

Priority: Plan (action score 40/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 4.4% (FIRST EPSS); higher than 91.3% of all records.
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
Fixed version: org.springframework.integration:spring-integration-core (Maven) 4.3.23, 5.1.12, 5.2.8.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Add it to your regular patch cycle. Upgrade to org.springframework.integration:spring-integration-core (Maven) 4.3.23, 5.1.12, 5.2.8 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

CriticalCVSS 9.8 · v3.1—No exploit Fix available

Published: Jul 31, 2020
Updated: Jun 16, 2026
EPSS: 4.4% · 91th percentile
CWE: CWE-502

Report tools

JSON

Action score

Plan

Add it to your regular patch cycle.

CVSS: 39 / 40 · 9.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 1 / 30 · 4.4%

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
vmware	spring integration	cpe:2.3:a:vmware:spring_integration
oracle	banking corporate lending process management	cpe:2.3:a:oracle:banking_corporate_lending_process_management
oracle	banking credit facilities process management	cpe:2.3:a:oracle:banking_credit_facilities_process_management
oracle	banking supply chain finance	cpe:2.3:a:oracle:banking_supply_chain_finance
oracle	banking virtual account management	cpe:2.3:a:oracle:banking_virtual_account_management
oracle	flexcube private banking	cpe:2.3:a:oracle:flexcube_private_banking
oracle	retail customer management and segmentation foundation	cpe:2.3:a:oracle:retail_customer_management_and_segmentation_foundation
oracle	retail merchandising system	cpe:2.3:a:oracle:retail_merchandising_system

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

oracle banking corporate lending process management14.2.0
oracle banking corporate lending process management14.3.0
oracle banking corporate lending process management14.5.0
oracle banking credit facilities process management14.2.0
oracle banking credit facilities process management14.3.0
oracle banking credit facilities process management14.5.0
oracle banking supply chain finance14.2.0
oracle banking supply chain finance14.3.0
oracle banking supply chain finance14.5.0
oracle banking virtual account management14.2.0
oracle banking virtual account management14.3.0
oracle banking virtual account management14.5.0
oracle flexcube private banking12.0.0
oracle flexcube private banking12.1.0
oracle retail customer management and segmentation foundation16.0 and later · up to 19.0 inclusive
oracle retail merchandising system16.0.3
vmware spring integration5.3.0 and later · up to 5.3.1 inclusive
vmware spring integration5.2.0 and later · up to 5.2.7 inclusive
vmware spring integration5.1.0 and later · up to 5.1.11 inclusive
vmware spring integration4.3.0 and later · up to 4.3.22 inclusive

Versions reported by the vendor

Affected version ranges reported by the assigning authority (pivotal). Independent of NVD's CPE analysis and usually ahead of it.

Spring by VMware Spring Integration
- 4.3 and later · before v4.3.23.RELEASEaffected
- 5.1 and later · before v5.1.12.RELEASEaffected
- 5.2 and later · before v5.2.8.RELEASEaffected
- 5.3 and later · before v5.3.2.RELEASEaffected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Maven	org.springframework.integration:spring-integration-core	from 4.3.0 · before 4.3.23	4.3.23
Maven	org.springframework.integration:spring-integration-core	from 5.1.0 · before 5.1.12	5.1.12
Maven	org.springframework.integration:spring-integration-core	from 5.2.0 · before 5.2.8	5.2.8
Maven	org.springframework.integration:spring-integration-core	from 5.3.0 · before 5.3.2	5.3.2

Same product

vmware: all records

Other highest-scoring records for the same primary product.

CVE-2026-47864Unsafe Java deserialization in SerializingHttpMessageConverter — remote code execution
41Plan
CVE-2019-3772Spring Integration XML External Entity Injection (XXE)
40Plan
CVE-2026-59324fluxTransform shared RequestMessageHolder causes cross-message header leakage under async fluxFunction
32Monitor

Published before and after this one in the same product

Later →CVE-2026-40987Jun 11, 2026 · Remote-file synchronizer in Spring Integration writes server-supplied filename under localDirectory without canonicalization
28Monitor
Later →CVE-2026-47856Aug 26, 2026 · JsonToObjectTransformer resolves the json__TypeId__ message header to an arbitrary class without an allow-list
25Monitor
Later →CVE-2026-47859Aug 26, 2026 · Unbounded memory allocation in RFC6587SyslogDeserializer (octet-counted framing) — remote DoS
26Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Maven:org.springframework.integration:spring-integration-core	4.3.23	Package registry (OSV)
Maven:org.springframework.integration:spring-integration-core	5.1.12	Package registry (OSV)
Maven:org.springframework.integration:spring-integration-core	5.2.8	Package registry (OSV)
Maven:org.springframework.integration:spring-integration-core	5.3.2	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

TR-21-0331 · Apr 21, 2021(Oracle Güvenlik Uyarısı Yayınladı)

All national notices →

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-502 · Deserialization of Untrusted Data

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Root cause

Data received over the network is deserialized into the language’s native object format without verifying its source. Code paths inside the object can be triggered during deserialization.

The bug in code

The whole CWE-502 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

python

1payload = sock.recv(65536)
2job = pickle.loads(payload)

Fixed

python

1payload = sock.recv(65536)
2if not hmac.compare_digest(sign(payload), header_sig):
3    raise PermissionError("invalid signature")
4job = JobSchema.validate(json.loads(payload))