CVE-2026-59444

Remote Code Execution
Affects
Spring Integration
in
Spring
No items found.
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

Patch Available.

Exclamation circle icon
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. It enables lightweight messaging within Spring-based applications and supports integration with external systems, such as Redis, through declarative adapters.

A remote code execution vulnerability (CVE-2026-59444) has been identified in the Spring Integration Redis queue endpoints, which allows attackers who can write to a Redis list consumed by one of these endpoints to make the application deserialize arbitrary classes. If a suitable gadget chain is present on the application's classpath, this can lead to remote code execution in the application process.

Per OWASP: Data which is untrusted cannot be trusted to be well formed. Malformed data or unexpected data could be used to abuse application logic, deny service, or execute arbitrary code, when deserialized.

This issue affects multiple versions of Spring Integration.

Details

Module Info

Vulnerability Info

This High-severity vulnerability is found in the org.springframework.integration:spring-integration-redis package in multiple versions of Spring Integration. Its CVSS 3.1 base score is 7.5 (AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H).

RedisQueueMessageDrivenEndpoint and RedisQueueInboundGateway pop raw bytes from a Redis list and deserialize them, and RedisQueueOutboundGateway deserializes the reply it reads back from Redis. Unless the application calls setSerializer(), each endpoint falls back to a plain JdkSerializationRedisSerializer when the container hands it the bean class loader:

@Override
public void setBeanClassLoader(ClassLoader beanClassLoader) {
	if (!this.serializerExplicitlySet) {
		this.serializer = new JdkSerializationRedisSerializer(beanClassLoader);
	}
}

The inbound endpoint then passes whatever it pops from the list straight to that serializer:

private void popMessageAndSend() {
	byte[] value = popForValue();
	...
	if (this.expectMessage) {
		try {
			message = (Message<Object>) this.serializer.deserialize(value);
		}
		...
	}
	else {
		Object payload = value;
		if (this.serializer != null) {
			payload = this.serializer.deserialize(value);
		}
		...
	}
	...
}

JdkSerializationRedisSerializer uses standard Java object deserialization and places no restriction on which classes may be instantiated. Any client with write access to the consumed Redis list (or, for the outbound gateway, to the reply list) can push a crafted serialized object graph, and the endpoint will reconstruct it in the application process. When a suitable gadget chain is available on the classpath, deserializing that object graph executes attacker-controlled code with the privileges of the application.

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.

Credits

  • Yu Bao from PayPal Cyber Security Team (finder)
Vulnerability Details
Severity
Level
CVSS Assessment
Low
>=0 <4
Medium
>=4 <6
High
>=6 <8
Critical
>=8 <10
High
ID
CVE-2026-59444
PROJECT Affected
Spring Integration
Versions Affected
<=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
NES Versions Affected
Published date
November 20, 2026
≈ Fix date
Category
Remote Code Execution
Vex Document
Download VEXHow do I use it?
Sign up for the latest vulnerability alerts fixed in
NES for Spring
Rss feed icon
Subscribe via RSS
or

By submitting the form I acknowledge receipt of our Privacy Policy.

Thanks for signing up for our Newsletter! We look forward to connecting with you.
Oops! Something went wrong while submitting the form.