Vulnerabilities

Spring Integration contains a race condition (CWE-362) in its reactive messaging support: when an IntegrationFlow uses .fluxTransform() with an asynchronous or reordering fluxFunction that emits raw payloads, per-message reply headers (replyChannel, errorChannel, correlationId, and propagated security/tenant headers) are not kept isolated. Under concurrent requests sharing the same FluxMessageChannel subscription, headers are copied from whichever message was most recently consumed upstream, so replies and security context can be attached to the wrong request. An attacker can therefore receive another user's response or have another session's or tenant's security headers applied to their exchange, producing cross-request and potentially cross-tenant information disclosure (high confidentiality, low integrity impact per the 8.2 CVSS score). Any application built on the affected Spring Integration versions (7.1.0, 7.0.0-7.0.5, 6.5.0-6.5.10, 6.4.0-6.4.12, or 5.5.21 and earlier) that uses this reactive pattern under concurrent load is affected. No public proof-of-concept is known, the flaw is not in CISA's KEV, and EPSS estimates only a 0.2% probability of exploitation in the next 30 days.

Do: Upgrade each deployed branch to a release beyond the affected ranges (later than 7.1.0, 7.0.5, 6.5.10, and 6.4.12; 5.5.x users should apply the latest 5.5 patch or migrate to a supported branch). Until patched, audit IntegrationFlows for .fluxTransform() with asynchronous or reordering fluxFunctions that emit raw payloads, and either avoid that pattern, prevent concurrent requests from sharing a single FluxMessageChannel subscription, or explicitly re-stamp replyChannel/errorChannel/correlationId and security/tenant headers per message. Also review whether cross-tenant or cross-session header leakage could have exposed sensitive data in past traffic.

Any application shipping logs to RabbitMQ over TLS via the Log4j2 appender, relying on the documented default, is exposed to man-in-the-middle interception of every log event. Spring AMQP 4.1.0 Spring AMQP 4.0.0 - 4.0.4 Spring AMQP 3.2.0 - 3.2.12 Spring AMQP 2.4.18 and earlier

ResourceCacheService.getCacheName() builds the on-disk filename by appending the URI fragment verbatim, without stripping path separators or .. sequences, and passes the result to new File(resourceParentFolder, newFileName) before writing the downloaded bytes there. Spring AI 2.0.0 Spring AI 1.1.0 - 1.1.8 Spring AI 1.0.9 and earlier

DeadLetterPublishingRecovererFactory reads the retry_topic-original-timestamp header from an inbound ConsumerRecord and passes its raw bytes directly to new BigInteger(header.value()) with no length or format validation. Spring for Apache Kafka 4.1.0 Spring for Apache Kafka 4.0.0 - 4.0.6 Spring for Apache Kafka 3.0.0 - 3.3.16 Spring for Apache Kafka 2.9.0 - 2.9.14 Spring for Apache Kafka 2.8.12 and earlier

Spring Cloud Config Server native environment repository allows exposure of configuration files outside of the configured repository path. Spring Cloud Config 5.0.0 - 5.0.4 Spring Cloud Config 4.3.0 - 4.3.4 Spring Cloud Config 4.0.0 - 4.2.8 Spring Cloud Config 3.1.14 and earlier

Spring MVC applications that use the functional web framework (functional endpoints) are vulnerable to stream corruption when serving Server-Sent Events (SSE) responses, a flaw classified as CWE-93 (improper neutralization of CRLF sequences in HTTP headers). The issue is triggered when an application streams SSE through these functional endpoints, corrupting the event stream framing; VMware rates the flaw Critical (CVSS 9.8, network-exploitable with no privileges or user interaction) with high confidentiality, integrity, and availability impact, though the advisory describes the outcome as stream corruption rather than a named attack primitive. Any application built on the affected Spring Framework branches that exposes SSE via functional endpoints is in scope. No public proof-of-concept, CISA KEV listing, or confirmed in-the-wild exploitation is known, and EPSS puts 30-day exploitation probability at 0.4%.

Do: Inventory Spring applications for use of the functional web framework (WebMvc.fn/functional endpoints) with SSE streaming and identify which of the affected branches (5.3.x through 7.0.x) they run. Upgrade each affected branch to a release beyond the last listed affected version per the VMware/Broadcom advisory, since fixes ship after 7.0.8, 6.2.19, 6.1.28, 6.0.30, and 5.3.49. As an interim mitigation, avoid serving SSE through functional endpoints or restrict access to those streaming routes.

Potential for deserialization of untrusted types in Spring Cloud Stream. Spring Cloud Stream 5.0.0 - 5.0.2 Spring Cloud Stream 4.3.0 - 4.3.3 Spring Cloud Stream 4.2.0 - 4.2.6

Potential arbitrary file read and SSRF vulnerability in Spring Cloud Function. Spring Cloud Function 5.0.0 - 5.0.3 Spring Cloud Function 4.3.0 - 4.3.4 Spring Cloud Function 4.2.0 - 4.2.7

CVE-2026-59285 is an unsafe deserialization flaw (CWE-502) in Spring for GraphQL, triggered when the framework processes paginated GraphQL queries. Because the attack vector is network-based with no privileges or user interaction required, a remote, unauthenticated attacker can send a crafted paginated query, though the high attack complexity rating means successful exploitation depends on conditions specific to each deployment. A successful attack could compromise the confidentiality, integrity, and availability of the application, potentially including remote code execution, without gaining privileges beyond the application's own scope. Only applications built with Spring for GraphQL versions 2.0.0 through 2.0.4 are affected; other versions are not implicated in this advisory. No public proof of concept, CISA KEV listing, or known in-the-wild exploitation exists, and EPSS estimates the 30-day exploitation probability at about 0.5%.

Do: Upgrade applications to a fixed Spring for GraphQL release beyond 2.0.4 per the vendor security advisory, and audit your dependency tree for spring-graphql versions 2.0.0 through 2.0.4. As an interim mitigation, require authentication and restrict network access to GraphQL endpoints, prioritizing internet-facing services, though the absence of a public PoC and the high attack complexity reduce urgency for internal deployments.

Spring Security's embedded UnboundID LDAP server (UnboundIdContainer) unconditionally registers an administrative credential and binds its listener to all available network interfaces. Spring Security 7.1.0 Spring Security 7.0.0 - 7.0.6 Spring Security 6.5.0 - 6.5.11 Spring Security 6.4.0 - 6.4.18 Spring Security 5.8.0 - 5.8.27 Spring Security 5.7.0 - 5.7.25