Deserialization in Spring Integration
CVE-2026-47856
Spring Integration's JSON to object conversion uses the json__TypeId__ header to choose the deserialization target type, and resolves that header value to a class with ClassUtils.forName and no type/package allow-list. Spring Integration 7.1.0 Spring Integration 7.0.0 - 7.0.5 Spring Integration 6.5.0 - 6.5.10 Spring Integration 6.4.0 - 6.4.12 Spring Integration 5.5.21 and earlier
Vulnerability class: Insecure Deserialization
Published · last modified .
CVSS v3 metric
CVSS v3 base score 6.3 (Medium). Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L.
EPSS exploit prediction
EPSS: 0.003 (22.3th percentile), scored .
Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 22nd percentile — 22.3% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.
EPSS over last 30 days · oldest: 0.002 · newest: 0.003 · change: +0.001
Affected products
- Spring Integration — versions 7.1.0
- VMware Spring Integration
Weakness classification (CWE)
References
- spring.io/security/cve-2026-47856 (Vendor Advisory)
Frequently asked questions
- What is CVE-2026-47856?
- CVE-2026-47856 is a medium-severity vulnerability in Spring Integration, classified under Deserialization of Untrusted Data. CVSS score: 6.3/10. Published 2026-08-27.
- How severe is CVE-2026-47856?
- Medium severity. CVSS v3 base score is 6.3 out of 10.