CVE-2026-59364
Patch Available.
This Vulnerability has been fixed in the Never-Ending Support (NES) version offered by HeroDevs.
Overview
Spring Integration extends the Spring programming model to support the well-known Enterprise Integration Patterns, enabling lightweight messaging within Spring-based applications and integration with external systems through declarative adapters such as FTP, SFTP, JMS and HTTP.
An information exposure vulnerability (CVE-2026-59364) has been identified in the DefaultFtpsSessionFactory class of the Spring Integration FTP module, which allows attackers with a man-in-the-middle position to impersonate an FTPS server. Because the server certificate chain and host name are not verified by default, an attacker can capture the FTP credentials sent during login and read or tamper with transferred files.
Per OWASP: Access control enforces policy such that users cannot act outside of their intended permissions. Failures typically lead to unauthorized information disclosure, modification, or destruction of all data or performing a business function outside the user's limits.
This issue affects multiple versions of Spring Integration.
Details
Module Info
- Product: Spring Integration
- Affected packages:
org.springframework.integration:spring-integration-ftp - Affected versions: <=5.5.22, >=6.0.0 <=6.4.13, >=6.5.0 <=6.5.11, >=7.0.0 <=7.0.7, >=7.1.0 <=7.1.2
- GitHub repository: https://github.com/spring-projects/spring-integration
- Published packages: https://central.sonatype.com/artifact/org.springframework.integration/spring-integration-ftp
- Package manager: Maven
- Fixed in:
- OSS Spring Integration 7.0.8, 7.1.3
- NES for Spring Integration
Vulnerability Info
This Medium-severity vulnerability is found in the org.springframework.integration:spring-integration-ftp package in multiple versions of Spring Integration. It has a CVSS 3.1 base score of 5.6 (AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L).
DefaultFtpsSessionFactory creates an Apache Commons Net FTPSClient for each FTPS session and configures it in postProcessClientBeforeConnect. A custom TrustManager is applied only when the application has explicitly set one:
@Override
protected void postProcessClientBeforeConnect(FTPSClient ftpsClient) {
JavaUtils.INSTANCE
.acceptIfHasText(this.authValue, ftpsClient::setAuthValue)
.acceptIfNotNull(this.trustManager, ftpsClient::setTrustManager)
.acceptIfNotNull(this.cipherSuites, ftpsClient::setEnabledCipherSuites)
.acceptIfNotNull(this.protocols, ftpsClient::setEnabledProtocols)
.acceptIfNotNull(this.sessionCreation, ftpsClient::setEnabledSessionCreation)
.acceptIfNotNull(this.useClientMode, ftpsClient::setUseClientMode)
.acceptIfNotNull(this.keyManager, ftpsClient::setKeyManager)
.acceptIfNotNull(this.needClientAuth, ftpsClient::setNeedClientAuth)
.acceptIfNotNull(this.wantsClientAuth, ftpsClient::setWantClientAuth);
}When no TrustManager is configured, the FTPSClient keeps its own default trust manager, TrustManagerUtils.getValidateServerCertificateTrustManager(). That trust manager only checks that each certificate is within its validity dates; it does not build or verify the certificate chain against a trust anchor. The factory also never enables endpoint checking on the client, so the host name in the server certificate is never compared with the host the application connected to.
As a result, an attacker who can intercept traffic between the application and the FTPS server can present any non-expired certificate, including a self-signed one, and the TLS handshake succeeds. The attacker can then proxy the connection, capture the user name and password sent with the FTP login commands, and read or modify files transferred over the session. Any application that uses DefaultFtpsSessionFactory without explicitly configuring a TrustManager that performs full certificate chain validation is affected.
Mitigation
Only recent versions of Spring Integration receive community support. Older lines are End-of-Life and will not receive public updates to address this issue.
Users of the affected components should apply one of the following mitigations:
- Upgrade to a currently supported version of Spring Integration.
- Leverage a commercial support partner like HeroDevs for post-EOL security support.