Vmware Spring Integration
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
What this means for your business
- It affects Vmware Spring Integration. It matters if your company, or a supplier that handles your data, runs it.
- An attacker can use it remotely, over a network, with an ordinary user login, and without anyone at your company clicking anything.
- FIRST's prediction model gives it a 4% chance of attack attempts being seen in the next 30 days, ranking above 90% of all known flaws.
What to do
- 1Check whether your company or your suppliers run Vmware Spring Integration, and which version. The affected versions are listed further down this page.
- 2If you do, apply the vendor's fix. A patch or vendor advisory has been published.
Not sure if your company is exposed?
Fastnexa’s certified penetration testers can check whether attackers could use this flaw, or others like it, against your websites, apps and network. The full test is free for our first 10 founding clients until 31 December 2026.
Scoring
- CVSS
- 6.4 (v3.1)
- Vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:L- Weakness
- CWE-502
- Assigned by
- security@vmware.com
Dates
- Published
- 2026-08-27
- Last modified
- 2026-09-02
- Sources
- NVD
Affected products
- Vmware Spring Integration- 5.5.22, 6.4.0 - 6.4.13, 6.5.0 - 6.5.11, 7.0.0 - 7.0.5.1, 7.1.0 - 7.1.0.1
As listed in the NVD configuration data. Not a statement about your estate.