Spring Integration
fluxTransform shared RequestMessageHolder causes cross-message header leakage under async fluxFunction
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
First public PoC
None yetno public PoC found
Public PoCs00 on GitHub
CVSS8.2high · scored by CNA · CWE-362
CISA KEV
Not listednot known exploited
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
Spring 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
Mitigation
The record names no fix. Check the vendor advisory below.
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.