CVE-2026-47864: Unsafe Java deserialization in SerializingHttpMessageConverter — remote code execution
Spring · Spring Integration
Affected: Spring Integration · Exploitation: possible (1 to 10%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 93% of scored CVEs
DescriptionCVE.org
SerializingHttpMessageConverter deserializes the body of incoming HTTP requests with a raw java.io.ObjectInputStream and no class filtering. Any request with Content-Type application/x-java-serialized-object whose body resolves to a Serializable type is read directly via readObject(). If an application using this converter on an inbound HTTP endpoint has any known Java deserialization "gadget" on its classpath, a remote, unauthenticated attacker can achieve arbitrary code execution. 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
Affected products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- Spring · Spring Integration7.1.0; from 7.0.0 up to and including 7.0.5; from 6.5.0 up to and including 6.5.10; from 6.4.0 up to and including 6.4.12; up to and including 5.5.21
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Possible (1 to 10%). EPSS between 1% and 10%.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- Spring
- Published
- August 2026
CoverageNo articles yet
No CyberSIXT article names CVE-2026-47864 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.