Skip to content
Fencer Vulns
medium 4.0

CVE-2026-41714 json

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

published 2026-06-09 5 mo ago modified 2026-08-12 2 mo ago also GHSA-p8qj-fj6r-w7q9 , EUVD-2026-35898

cvss
4.0
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.1%
EPSS 0.1% chance of exploitation in 30 days, percentile 2%
public exploits
0
none known

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.

Patch / fix

  • maven org.springframework.amqp:spring-amqp 3.2.11, 4.0.4
  • Spring Spring AMQP 2.4.18, 3.1.16, 3.2.10.1, 4.0.3.1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-41714 updated cvss 5.9

spring-amqp: Spring AMQP: Lack of certificate validation in TLS connections

  • Red Hat build of Apache Camel 4 for Quarkus 3 spring-amqp
    affected: workaround, no fix available “When using RabbitConnectionFactoryBean.setUri() with an amqps:// URI, explicitly call setUseSSL(true) to enable proper certificate validation and hostname verification.”
  • Red Hat Fuse 7 spring-amqp
    affected: workaround, no fix planned “When using RabbitConnectionFactoryBean.setUri() with an amqps:// URI, explicitly call setUseSSL(true) to enable proper certificate validation and hostname verification.”
  • Red Hat JBoss Enterprise Application Platform Expansion Pack spring-amqp
    affected: workaround, no fix available “When using RabbitConnectionFactoryBean.setUri() with an amqps:// URI, explicitly call setUseSSL(true) to enable proper certificate validation and hostname verification.”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
4 mo ago

Exploit prediction

0.13% chance of exploitation in the next 30 days, higher than 2% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 4.0 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:N
GitHub 3.1 4.0 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:N

Affected packages

ecosystem package affected fixed in
maven org.springframework.amqp:spring-amqp
>=4.0.0, <4.0.4
>=3.2.0, <3.2.11
>=3.1.0, <=3.1.15
<=2.4.17
4.0.4
3.2.11

Affected products

  • Spring Spring AMQP

Classification

Weakness
  • CWE-295 Improper Certificate Validation

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.