Quick answers
- Is CVE-2026-47864 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-47864 being exploited in the wild.
- How severe is CVE-2026-47864?
- Medium severity, with a CVSS score of 6.4, published 27 August 2026.
- Which products and versions are affected?
- Spring Integration 7.1.0, 7.0.0–7.0.5, 6.5.0–6.5.10, 6.4.0–6.4.12, 5.5.21 and earlier.
- Is there a fix for CVE-2026-47864?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-47864 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-47864?
- Check whether you run Spring Integration at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a Java deserialization flaw in SerializingHttpMessageConverter, which processes incoming HTTP requests with Content-Type application/x-java-serialized-object by directly calling readObject() on a raw ObjectInputStream without any gadget filtering or class validation. The vulnerability affects multiple versions: Spring Integration 7.1.0, 7.0.0–7.0.5, 6.5.0–6.5.10, 6.4.0–6.4.12, and 5.5.21 and earlier. Remote unauthenticated attackers can exploit this by sending a crafted serialized Java object in an HTTP request body; successful exploitation requires the presence of a deserialization gadget chain (such as from Apache Commons Collections or similar libraries) on the application's classpath, allowing arbitrary code execution. No patch availability information is documented in the provided advisory text.
Affected products
- Spring Integration 7.1.0, 7.0.0–7.0.5, 6.5.0–6.5.10, 6.4.0–6.4.12, 5.5.21 and earlier
Timeline
- 2026-08-27: disclosed