fluxTransform shared RequestMessageHolder causes cross-message header leakage under async fluxFunction
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. No fixed version is recorded.
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
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Spring | <=5.5.21, =7.1.0, >=6.4.0 <=6.4.12, >=6.5.0 <=6.5.10, >=7.0.0 <=7.0.5 |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket