CVE-2026-41714Applications that configure their broker connection via RabbitConnectionFactoryBean.setUri("amqps://...") without also calling setUseSSL(true) get TLS encryption with no certificate validation and no…
Updated under an hour ago ()
Does this affect you?
It affects vmware spring_advanced_message_queuing_protocol. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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
- 4.0 MEDIUM (v3.1, NVD)CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:N
- Weakness (CWE)
- CWE-295
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Not given
- NVD analysis
- Analyzed
- Record last updated
- Jul 23, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
vmware spring_advanced_message_queuing_protocol vmware:spring_advanced_message_queuing_protocol | before 2.4.18; from 3.1.0 before 3.1.16; from 3.2.0 before 3.2.10.1; from 4.0.0 before 4.0.3.1 | NVD |
References
- https://spring.io/security/cve-2026-41714vendor-advisory
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.