CVE-20XX-?

VMware Spring Integration CVEs.

Published CVEs affecting VMware Spring Integration, ranked by exploit odds.

3 CVEs · updated 2026-11-06 10:55 UTC

Reset all
  1. CVE-2026-47864

    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

    Code execution VMware Spring Integration

    6.4 MEDIUM 6% exploit odds Fix listed
  2. CVE-2026-59307

    An operator who calls JdbcMessageStore.addAllowedPatterns(...) to restrict deserialization receives no protection at all when the store is a Spring-managed bean. 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

    Code execution VMware Spring Integration

    8.0 HIGH 0.4% exploit odds Fix listed
  3. 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

    Code execution Library VMware Spring Integration

    6.3 MEDIUM 0.3% exploit odds Fix listed

All CVEs affecting VMware Spring Integration that appear in CVE.org and NVD, sorted by how likely they are to be exploited (EPSS), with fix status and timeline.