Medium severity · published Jun 9, 2026
CVE-2026-41714
In Spring AMQP the RabbitConnectionFactoryBean.setUri("amqps://...") bypasses secure SSL setup, uses TrustEverythingTrustManager
4.0
CVSS
0.1%
EPSS
No
On KEV
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.
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:N
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Confidentiality
Low
Integrity
None
Availability
None
Scope
Changed
Exploitation
Is it being used?
Exploit prediction (EPSS)0.1% · higher than 3% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
SA
Spring AMQP · Spring
4.0.0 before 4.0.3.1; 3.2.0 before 3.2.10.1; 3.1.0 before 3.1.16; 2.4.0 before 2.4.18 · source: vendor
SA
Spring Advanced Message Queuing Protocol · Vmware
before 2.4.18; 3.1.0 before 3.1.16; 3.2.0 before 3.2.10.1; 4.0.0 before 4.0.3.1 · source: NVD
Affected product
SA
Spring AMQP
Spring
More from Spring AMQP
6.8
CVE-2026-59272
Log4j2 AmqpAppender disables TLS hostname verification by default
6.5
CVE-2026-59320
In Spring AMQP the link credit never replenished on listener exception path
6.5
CVE-2026-59271
Admin password disclosed in BrokerNotAliveException message
6.5
CVE-2026-47860
Unbounded decompression of attacker-supplied compressed message bodies
4.9
CVE-2026-59275
Remote JVM termination: nested-array Java deserialization bypasses allowlist, triggers StackOverflowError, default JavaLangErrorHandler calls System.exit(99)