CVE Watchtower

CVE-2026-59365Spring Integration Improper Input Validation

Spring

Vulnerability Summary

Spring Integration AMQP Default Inbound Header Mapper Maps replyChannel and errorChannel Headers. With its default inbound request header pattern of *, DefaultAmqpHeaderMapper.inboundMapper() copies all AMQP application headers into the Spring Integration message headers, including the framework-significant replyChannel and errorChannel headers. This mapper is used by default by all AMQP inbound components, such as AmqpInboundChannelAdapter, AmqpInboundGateway, AmqpMessageSource and AMQP-backed message channels. An attacker able to publish messages to a RabbitMQ queue consumed 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, to another channel in the application.
Severity Level
MEDIUM(6.3)
Published Date
Nov 19, 2026
Last Modified
Nov 19, 2026
Exploitation Status
No confirmed exploitation yet
CVE Record Status
Reserved
This CVE ID is referenced in a public advisory, but the CVE Program has not published its official CVE Record yet. Full CVSS/CPE data from NVD will appear here once it does.
Root Weakness (CWE)
The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required.
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
See the MITRE CWE entry for the full definition of this weakness.
The product receives input from an upstream component that specifies multiple attributes, properties, or fields that are to be initialized or updated in an object, but it does not properly control which attributes can be modified.
CVSS v3.1 Base Metrics — Score 6.3 (MEDIUM)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredLow
User InteractionNone
ScopeUnchanged
ConfidentialityLow
IntegrityLow
AvailabilityLow

Affected & Patched Versions

Affected 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 through 5.5.22
Patched Versions
  • 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.

  1. Check whether you run Spring Integration and which version.
  2. 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-59365. Get an email when KEV listings, exploits or new CVEs match your stack.
Set up CVE alerts

More Spring Integration CVEs

External References

Data last checked: Nov 20, 2026 05:01 UTC