CVE-2026-59324

Analyzed Analyzed - Analysis Complete

Concurrent Reply Header Corruption in Spring Integration

Publication date: 2026-08-27

Last updated on: 2026-09-01

Assigner: VMware

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 Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-08-27

Last Modified

2026-09-01

Generated

2026-09-17

AI Q&A

2026-08-28

EPSS Evaluated

2026-09-15

NVD

CVE-2026-59324

Affected Vendors & Products

Vendor	Product	Version / Range
vmware	spring_integration	From 6.4.0 (inc) to 6.4.13 (exc)
vmware	spring_integration	From 6.5.0 (inc) to 6.5.11 (exc)
vmware	spring_integration	From 7.0.0 (inc) to 7.0.5.1 (exc)
vmware	spring_integration	From 7.1.0 (inc) to 7.1.0.1 (exc)
vmware	spring_integration	to 5.5.22 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-362	The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

Attack-Flow Graph

Executive Summary

CVE-2026-59324 affects Spring Integration versions 7.1.0 and earlier. It occurs when an IntegrationFlow uses .fluxTransform() with an asynchronous or reordering fluxFunction that emits raw payloads. Concurrent requests on the same FluxMessageChannel subscription may have their reply headers copied from the most recently consumed message upstream. This can cause reply mis-routing where one user's response payload is delivered to another user's reply channel.

Detection Guidance

Detecting this vulnerability requires checking the Spring Integration version in use. Commands like 'find / -name "spring-integration*.jar" 2>/dev/null | xargs -I {} sh -c "echo -n {}" | xargs -I {} sh -c "jar tf {} | grep -i IntegrationFlow.class"' can help locate the library. Verify the version in dependency files (pom.xml, build.gradle) or via 'java -cp <path-to-spring-integration.jar> org.springframework.integration.version.VersionInfo'.

Impact Analysis

This vulnerability can lead to cross-request information disclosure. Attackers may intercept or receive sensitive data intended for other users due to reply header mis-routing. It primarily impacts confidentiality with a low impact on integrity according to CVSS scoring.

Compliance Impact

This vulnerability could lead to cross-request information disclosure by misrouting reply payloads between users. This may violate GDPR's data protection principles (Article 5) and HIPAA's security rule (45 CFR 164.312) by exposing sensitive user data to unauthorized parties through improper header handling.

Mitigation Strategies

Upgrade to fixed versions: 7.1.0.1 (Enterprise), 7.1.1 (OSS), 7.0.5.1 (Enterprise), 7.0.6 (OSS), 6.5.11 (Enterprise), 6.4.13 (Enterprise), or 5.5.22 (Enterprise).
If upgrading is not possible, modify the fluxFunction signature to Function<? super Flux<Message<I>>, ? extends Publisher<Message<O>>> as a partial mitigation.

Hi! I’m here to help you understand CVE-2026-59324. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70