CVE-2026-41714GHSA-P8QJ-FJ6R-W7Q9
In Spring AMQP the RabbitConnectionFactoryBean.setUri("amqps://...") bypasses secure SSL setup, uses TrustEverythingTrustManager
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 4.0.3.1, 3.2.10.1, 3.1.16, 2.4.18, 4.0.4, and 1 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Spring Spring AMQP
From 4.0.0 · fixed in 4.0.3.1; From 3.2.0 · fixed in 3.2.10.1; From 3.1.0 · fixed in 3.1.16; From 2.4.0 · fixed in 2.4.18
- org.springframework.amqp:spring-amqpMaven
From 4.0.0 · fixed in 4.0.4
- org.springframework.amqp:spring-amqpMaven
From 3.2.0 · fixed in 3.2.11
- org.springframework.amqp:spring-amqpMaven
From 3.1.0 · through 3.1.15
- org.springframework.amqp:spring-amqpMaven
through 2.4.17