Quick answers
- Is CVE-2026-47859 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-47859 being exploited in the wild.
- How severe is CVE-2026-47859?
- Medium severity, with a CVSS score of 5.4, published 27 August 2026.
- Which products and versions are affected?
- Spring Integration 5.5.21 and earlier, 6.4.0–6.4.12, 6.5.0–6.5.10, 7.0.0–7.0.5, 7.1.0.
- Is there a fix for CVE-2026-47859?
- 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-47859 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-47859?
- 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 RFC6587SyslogDeserializer component in Spring Integration, used by the syslog TCP inbound adapter, trusts an octet count field from untrusted RFC 5424 / RFC 6587 frames without validation. An attacker can provide an arbitrarily large octet count, causing the deserializer to allocate a byte array of that exact size with no upper bound checks. This leads to memory exhaustion and denial of service. The vulnerability affects 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. The attack vector is network-based and requires only the ability to send data to the syslog TCP inbound adapter.
Affected products
- Spring Integration 5.5.21 and earlier, 6.4.0–6.4.12, 6.5.0–6.5.10, 7.0.0–7.0.5, 7.1.0
Timeline
- 2026-08-27: disclosed: CVE-2026-47859 published