CVE-2026-59307: Deserialization allow-list silently bypassed: setBeanClassLoader replaces deserializer but mapper keeps stale reference
An operator who calls JdbcMessageStore.addAllowedPatterns(...) to restrict deserialization receives no protection at all when the store is a Spring-managed bean. Spring Integration 7.1.0 Spring Integration 7.0.0 - 7.0.5 Spring Integration 6.5.0 - 6.5.10 Spring Integration 6.4.0 - 6.4.12
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Spring Integrationto a version that resolves this vulnerability.Fixed in 6.4.12 - Upgrade
Upgrade
Spring Integrationto a version that resolves this vulnerability.Fixed in 6.5.10 - Upgrade
Upgrade
Spring Integrationto a version that resolves this vulnerability.Fixed in 7.0.5 - Upgrade
Upgrade
Spring Integrationto a version that resolves this vulnerability.Fixed in 7.1.0
Event History
Frequently Asked Questions
Which deployments are affected?
Affected deployments use a Spring-managed JdbcMessageStore and call JdbcMessageStore.addAllowedPatterns(...) to restrict deserialization. In that configuration, the intended allow-list protection is silently bypassed.
Which Spring Integration versions are listed as affected?
The listed affected versions are 7.1.0, 7.0.0 through 7.0.5, 6.5.0 through 6.5.10, and 6.4.0 through 6.4.12.