Skip to main content

Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') in org.springframework.integration:spring-integration-core

CVE-2026-59324

  • org.springframework.integration:spring-integration-core
High
8.2/10

Summary

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. This issue affects Spring Integration versions through 5.5.21, 6.4.0 through 6.4.12, 6.5.0 through 6.5.10, 7.0.0 through 7.0.5 and 7.1.0.

  • LOW
  • NETWORK
  • LOW
  • UNCHANGED
  • NONE
  • NONE
  • HIGH
  • NONE

CWE-362 - Race Condition

A race condition occurs in a shared memory program when two threads/processes access the same shared memory data, and at least one thread executes a write operation. This vulnerability manipulates the time to check vs. time to use (TOC/TOU) gap between the threads in the critical section to cause disorientation in the shared data. The impact can vary from compromising the confidentiality of the system to causing the system to crash or to execute arbitrary code.

References

Advisory Timeline

  • Published