CVE-2026-59324
- Published27 Aug 2026
Description
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
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:NAffected products
Remediation
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-59324 being actively exploited?
CVE-2026-59324 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.24%.
How severe is CVE-2026-59324?
CVE-2026-59324 has a CVSS 3.1 base score of 8.2, rated high. EPSS estimates a 0.24% probability of exploitation.
Which products are affected by CVE-2026-59324?
Affected products include Vmware Spring Integration.
How do I fix CVE-2026-59324?
Upgrade affected software to a fixed version, for example Vmware Spring Integration 6.4.13 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-59324 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.