Skip to content
fr Sign in
4.0 Medium

CVE-2026-41714 Applications that configure their broker connection via RabbitConnectionFactoryBean.setUri("amqps://...") without also…

Description

Applications that configure their broker connection via RabbitConnectionFactoryBean.setUri("amqps://...") without also calling setUseSSL(true) get TLS encryption with no certificate validation and no hostname verification. Affected versions: Spring AMQP 4.0.0 through 4.0.3; 3.2.0 through 3.2.10; 3.1.0 through 3.1.15; 2.4.0 through 2.4.17.

Affected products and versions

Product Affected versions Fixed in
Spring AMQP 4.0 4.0.0 → < 4.0.3.1 4.0.3.1
Spring AMQP 3.2 3.2.0 → < 3.2.10.1 3.2.10.1
Spring AMQP 3.1 3.1.0 → < 3.1.16 3.1.16
Spring AMQP 2.4 2.4.0 → < 2.4.18 2.4.18

References

Timeline

  1. Published
  2. Last modified

Other CVEs of Spring AMQP

The 8 CVEs of Spring AMQP →
CVE-2026-59320 When a container-level ErrorHandler is configured (the mitigation for finding 221000), each delivery whose processing… 6.5 Medium CVE-2026-59272 Any application shipping logs to RabbitMQ over TLS via the Log4j2 appender, relying on the documented default, is… 6.8 Medium CVE-2026-59275 A single hostile AMQP message can terminate the entire consumer JVM (System.exit(99)), not just the listener thread —… 6.6 Medium CVE-2026-59271 When the RabbitMQ management aliveness check fails, the configured admin password is embedded in cleartext in the thrown… 5.3 Medium
Track this CVE