vulntracker.iovulntracker.io
© 2026 vulntracker.io

CVE-2026-41714

In Spring AMQP the RabbitConnectionFactoryBean.setUri("amqps://...") bypasses secure SSL setup, uses TrustEverythingTrustManager

MEDIUM
4
CVSS Score
Published: June 9, 2026 at 11:48 PM UTC
Updated: July 23, 2026 at 07:32 PM UTC
2 products affected across 2 vendorsSpring Advanced Message Queuing ProtocolSpring Advanced Message Queuing Protocol

Using Spring AMQP by Spring?

Get instant alerts when new vulnerabilities affect Spring AMQP - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Start FreeSign In
Severity
MEDIUM4
Exploit prediction
EPSS 0.1%
SSVC
No known exploit

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

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Spring Advanced Message Queuing Protocol· VMware
95%
v < 2.4.183.1.0 ≤ v < 3.1.163.2.0 ≤ v < 3.2.10.14.0.0 ≤ v < 4.0.3.1
Affected range stops below 2.4.18, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.1.16, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.2.10.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.0.3.1, so it looks safe — our inference, not a vendor statement
Spring Advanced Message Queuing Protocol· Spring
60%
2.4.0 ≤ v < 2.4.183.1.0 ≤ v < 3.1.163.2.0 ≤ v < 3.2.10.14.0.0 ≤ v < 4.0.3.12.4.03.1.03.2.04.0.0
Affected range stops below 2.4.18, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.1.16, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.2.10.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.0.3.1, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

References (1)

Vendor Advisory
Source: cverecord
https://spring.io/security/cve-2026-41714

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

4MEDIUMvmware
Attack Vector
NETWORK
Complexity
HIGH
Privileges
NONE
User Interaction
NONE
Scope
CHANGED
Confidentiality
LOW
Integrity
NONE
Availability
NONE
Vector?

Quick Info

StatusANALYZED
CWE
CWE-295

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create accountSign in
Free plan, no card