CVE-2026-59405
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, including an XMPP adapter for chat and presence messaging.
An information exposure vulnerability (CVE-2026-59405) has been identified in the XmppConnectionFactoryBean of Spring Integration XMPP, which allows attackers on the network path to the XMPP server to strip the STARTTLS negotiation and read the connection's credentials and messages in cleartext. The same position also lets an attacker inject XMPP messages that the integration flow treats as legitimate.
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-xmpp - Affected versions: <=5.5.22, >=6.4.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-xmpp
- Package manager: Maven
- Fixed in:
- OSS Spring Integration 7.0.8, 7.1.3
- NES for Spring Integration
Vulnerability Info
This Low-severity vulnerability is found in the org.springframework.integration:spring-integration-xmpp package in multiple versions of Spring Integration. Spring rates it CVSS 3.1 2.2 (AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:N/A:N).
When an application does not supply its own XMPPTCPConnectionConfiguration, XmppConnectionFactoryBean.createInstance() builds one from the configured host, port, user and password, but never calls setSecurityMode:
protected XMPPConnection createInstance() throws XmppStringprepException {
XMPPTCPConnectionConfiguration connectionConfig = this.connectionConfiguration;
if (connectionConfig == null) {
XMPPTCPConnectionConfiguration.Builder builder =
XMPPTCPConnectionConfiguration.builder()
.setHost(this.host)
.setPort(this.port);
if (StringUtils.hasText(this.resource)) {
builder.setResource(this.resource);
}
if (StringUtils.hasText(this.serviceName)) {
builder.setUsernameAndPassword(this.user, this.password)
.setXmppDomain(this.serviceName);
}
else {
builder.setUsernameAndPassword(XmppStringUtils.parseLocalpart(this.user), this.password)
.setXmppDomain(this.user);
}
connectionConfig = builder.build();
}
return new XMPPTCPConnection(connectionConfig);
}The connection therefore inherits the security mode default of the Smack library on the classpath. In Smack 4.3.x, the version Spring Integration 5.5.x depends on, ConnectionConfiguration.Builder defaults to SecurityMode.ifpossible, so TLS is negotiated only if the server advertises STARTTLS. That feature is advertised in the cleartext stream-features stanza, so an on-path attacker can remove it, and the client silently continues without encryption. The configured credentials (or the SCRAM exchange) and all later message traffic are then sent in plaintext.
Applications are affected when they let XmppConnectionFactoryBean create the XMPP connection, rather than supplying their own XMPPTCPConnectionConfiguration, and when an attacker can actively interpose on the network path to the XMPP server. Applications that cannot upgrade can supply their own XMPPTCPConnectionConfiguration built with setSecurityMode(ConnectionConfiguration.SecurityMode.required).
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.