CVE-2026-59363Spring Integration Improper Input Validation
Spring
Vulnerability Summary
Spring Integration MQTT v5 Header Mapper Maps All User Properties Including Framework-Significant Headers. MQTT v5 PUBLISH packets carry arbitrary user properties supplied by the publisher. With its default inboundHeaderNames of *, MqttHeaderMapper maps every user property into the message headers without excluding framework-significant names such as replyChannel and errorChannel, and Mqttv5PahoMessageDrivenChannelAdapter builds the message directly from those headers. An attacker able to publish to a topic subscribed by an affected application can therefore set these headers. A replyChannel or errorChannel header is later resolved as a MessageChannel bean name, which allows the attacker to redirect the output of reply-producing handlers without an explicit output channel, or error messages (embedding the attacker payload), to another channel in the application, for example one that forwards to an external system. Applications using Mqttv5PahoMessageDrivenChannelAdapter with the default header mapping are affected. Affected artifact: org.springframework.integration:spring-integration-mqtt.
CVSS v3.1 Base Metrics — Score 5.4 (MEDIUM)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:NAttack VectorNetwork
Attack ComplexityLow
Privileges RequiredLow
User InteractionNone
ScopeUnchanged
ConfidentialityLow
IntegrityLow
AvailabilityNone
Affected & Patched Versions
- Spring Integration 7.1.0 through 7.1.2
- Spring Integration 7.0.0 through 7.0.7
- Spring Integration 6.5.0 through 6.5.11
- Spring Integration 6.0.0 through 6.4.13
- Spring Integration 5.5.5 through 5.5.22
- Spring Integration 7.1.3 (open source)
- Spring Integration 7.0.8 (open source)
- Spring Integration 7.1.2.1 (commercial support only)
- Spring Integration 7.0.7.1 (commercial support only)
- Spring Integration 6.5.12 (commercial support only)
- Spring Integration 6.4.14 (commercial support only)
- Spring Integration 5.5.23 (commercial support only)
What to do
Fix it during your normal patch cycle. No exploitation is confirmed yet.
- Check whether you run Spring Integration and which version.
- Update to a patched version listed above, then confirm the new version.
Timeline
- Nov 19, 2026Published
- Nov 19, 2026Record last modified
Score, severity and exploitation changes are tracked from the day Watchtower started logging them.
Get notified about new Spring Integration CVEsYou are reading CVE-2026-59363. Get an email when KEV listings, exploits or new CVEs match your stack.
Set up CVE alertsMore Spring Integration CVEs
External References
- Vendor Advisoryhttps://spring.io/security/cve-2026-59363
Data last checked: Nov 20, 2026 05:01 UTC