Get ahead
VMware offers training and certification to turbo-charge your progress.
Learn moreThe fix for CVE-2026-59307 introduced a regression in JdbcMessageStore. When the store is configured as a <bean> or via @Bean, the Spring container populates properties (including addAllowedPatterns()) before invoking the BeanClassLoaderAware callback. setBeanClassLoader() then replaces the deserializer with a new, empty AllowListDeserializingConverter and rebinds the message row mapper to it, discarding the previously registered allowed patterns. Since an empty allow-list permits all types, the store deserializes any class present on the classpath from the INT_MESSAGE.MESSAGE_CONTENT column, silently defeating the allow-list the operator configured.
Applications are affected if they use JdbcMessageStore with an allow-list of deserializable types configured through addAllowedPatterns() on a Spring-managed bean, and an attacker is able to write to the message store table.
Spring Integration:
| Fix version | Availability |
|---|---|
| 7.1.3 | OSS |
| 7.1.2.1 | Enterprise Support Only |
| 7.0.8 | OSS |
| 7.0.7.1 | Enterprise Support Only |
| 6.5.12 | Enterprise Support Only |
| 6.4.14 | Enterprise Support Only |
Users of affected versions who cannot upgrade can configure the JdbcMessageStore with an explicit deserializer via setDeserializer(), providing an AllowListDeserializingConverter with the required allowed patterns, so that setBeanClassLoader() does not replace it. Restricting write access to the message store tables to the application only further reduces the risk.
This vulnerability was discovered and responsibly reported by Scott Frederick at HeroDevs.
To report a security vulnerability for a project within the Spring portfolio, see the Security Policy