High [CVE-2026-59324] org.springframework.integration/spring-integration-core: Spring Integration: Information disclosure via cross-message header leakage
This high-severity Red Hat Linux advisory covers CVE-2026-59324 affecting Red Hat Fuse 7.
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.
Summary
A flaw was found in Spring Integration. When an IntegrationFlow uses `.fluxTransform()` with an asynchronous `fluxFunction` that emits raw payloads, concurrent requests on the same `FluxMessageChannel` subscription can have their reply headers copied from other messages.
This information disclosure vulnerability allows an attacker to potentially access sensitive data such as `replyChannel`, `errorChannel`, `correlationId`, or other security-related headers from concurrent requests.
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 severity: Important — CVSS 8.2 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N).
Weakness: CWE-821. Affected Red Hat products: Red Hat Fuse 7.
Red Hat does not currently list a fixing RHSA for this CVE.
Affected versions
No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.
Official advisory · high-confidence parse· fetched 2 hours ago·verify at source
Fixed versions
No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.
Official advisory · high-confidence parse· fetched 2 hours ago·verify at source
Mitigation checklist
- 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.
Official advisory · high-confidence parse· fetched 2 hours ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.