cve.bz

CVE-2026-59324 vmware spring integration: Race Condition

8.2 highEPSS 0.3%

High (8.2) in vmware spring integration. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
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

Severity

CVSS 3.1

8.2 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 20th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-08-28. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization (Race Condition)
OWASP Top 10
A06:2025 Insecure Design
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-59324 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-59324?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-59324?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-59324 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Spring Integration7.1.0
Spring Integrationfrom 7.0.0 through 7.0.5
Spring Integrationfrom 6.5.0 through 6.5.10
Spring Integrationfrom 6.4.0 through 6.4.12
Spring Integrationthrough 5.5.21

Red Hat

Red Hat rates this Important.

Red Hat's statement

A concurrency-related context leakage vulnerability exists in Spring Integration's reactive fluxTransform() function when processing raw payloads on a shared FluxMessageChannel. Under concurrent request loads, the transformer copies message headers—including replyChannel, errorChannel, correlationId, and security or tenant context—from the most recently consumed upstream message rather than maintaining request isolation. Unauthenticated remote attackers sending concurrent requests can intercept sensitive routing headers and cross-tenant security tokens, leading to information disclosure and potential message misrouting across session boundaries.

Red Hat's mitigation

Avoid using raw payload emission inside asynchronous fluxTransform() functions on shared FluxMessageChannel subscriptions, or wrap reactive emissions in Message<T> instances to preserve header isolation per request.

ProductPackageStateAdvisory
Red Hat Fuse 7spring-integration-coreNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-59324.

Attack patterns (CAPEC)

  • CAPEC-26 Leveraging Race Conditions Likelihood: High · Severity: High
  • CAPEC-29 Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON