Advisoriesby IbisVMwareCVE-2026-59324
VMware Spring Integration: race condition
No fix yet
When an IntegrationFlow uses .fluxTransform() with an asynchronous/reordering fluxFunction that emits raw payloads, concurrent requests on the same FluxMessageChannel subscription have their reply headers (replyChannel, errorChannel, correlationId, any propagated security/tenant headers) copied from whichever message was most recently consumed upstream.
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
Affected versions
| Package | Affected | Fixed in |
|---|---|---|
| Spring Integration Product | <= 7.1.0 | No fix yet |
| >= 7.0.0, <= 7.0.5 | No fix yet | |
| >= 6.5.0, <= 6.5.10 | No fix yet | |
| >= 6.4.0, <= 6.4.12 | No fix yet |
Details and references
- CVSS 3.1
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
- Severity from
- the vendor (its own CVE record or advisory)
- Weakness
- CWE-362