CVE-2026-47864 PUBLISHED

Unsafe Java deserialization in SerializingHttpMessageConverter — remote code execution

Assigner: vmware
Reserved: 20.05.2026 Published: 27.08.2026 Updated: 27.08.2026

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

Metrics

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

Product Status

Vendor Spring
Product Spring Integration
Versions Default: unaffected
  • Version 7.1.0 is affected
  • affected from 7.0.0 to 7.0.5 (incl.)
  • affected from 6.5.0 to 6.5.10 (incl.)
  • affected from 6.4.0 to 6.4.12 (incl.)
  • affected from 0 to 5.5.21 (incl.)

References

Problem Types

  • CWE-502 Deserialization of Untrusted Data CWE

Impacts

  • 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.